/

CVE-2026-84423

Severity:

HIGH RISK

(7.3)

Missing Authentication (CWE-306) in Casdoor Upload API

CVE-2026-84423

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-287, CWE-306

Impact:

Unauthorized Resource Upload and Application Integrity Compromise

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Casdoor contains a missing-authentication vulnerability in the upload-resource API, allowing remote requests to reach the resource upload functionality without the expected authentication checks. Depending on deployment permissions and endpoint behavior, an unauthenticated attacker may upload or alter resources and affect application content or workflows.

Affected context

The issue affects Casdoor deployments exposing the upload-resource API implemented in controllers/resource.go. It becomes risky when the endpoint is reachable over a network and does not consistently require authentication and authorization before processing upload requests. The practical impact depends on how uploaded resources are stored, served, and trusted by the surrounding application.

Exploit preconditions

  • Attack surface: The remotely reachable upload-resource API
  • Required access: No valid application authentication may be required
  • Trigger point: A request reaching the resource upload handler
  • Why exploitation is possible: The endpoint can process the operation without first enforcing the authentication and authorization controls expected for the resource-management function

Why this happens

The underlying bug is an authorization boundary failure: a sensitive API operation is exposed without a reliable authentication check before request processing. This maps primarily to CWE-306: Missing Authentication for Critical Function. It is also related to CWE-287: Improper Authentication, because the endpoint does not adequately establish the identity required to perform the operation. The insecure pattern is treating an externally supplied request as eligible for a privileged action without consistently verifying identity and permissions.

Potential impact

  • An unauthenticated party may upload or modify application resources
  • Hosted content or application behavior could be altered
  • Users may be exposed to unauthorized or malicious content
  • Application integrity and operational workflows may be disrupted
  • Uploaded resources could contribute to broader compromise if later trusted as executable or privileged content

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization at the API boundary before any resource operation is performed.

Common defensive patterns include:

  • Require authenticated sessions or equivalent strong identity proof for resource-management endpoints
  • Apply explicit, server-side authorization checks based on resource ownership and least privilege
  • Use secure-by-default routing and middleware so newly exposed endpoints inherit authentication requirements
  • Treat uploaded content as untrusted, validate it against an allowlist, and store it outside executable or privileged paths
  • Separate public read access from privileged upload and modification operations
  • Use narrowly scoped service identities and storage permissions for the upload process
  • Apply request-size, type, and destination restrictions without treating validation as a substitute for authentication

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and route audits that flag sensitive handlers lacking authentication middleware
  • Code review checks verifying authentication and authorization occur before file or resource processing
  • API inventory comparisons to ensure every upload, update, and delete operation has an explicit access policy
  • Integration tests that send unauthenticated requests to protected endpoints and verify denial
  • Gateway or policy enforcement requiring identity-aware access for resource-management routes
  • Monitoring for anonymous upload attempts, unusual upload volumes, and unexpected resource changes

Automated review tools may help detect routes whose protection differs from neighboring privileged endpoints.

Sources

SourceLink
github.comgithub.com/casdoor/casdoor/
github.comgithub.com/casdoor/casdoor/issues/5617
github.comgithub.com/geo-chen/oss/blob/main/casdoor.md#finding-1-unauthenticated-arbitrary-file-upload-via-apiupload-resource
vuldb.comvuldb.com/cve/CVE-2026-84423
vuldb.comvuldb.com/submit/883037
vuldb.comvuldb.com/vuln/397791
vuldb.comvuldb.com/vuln/397791/cti

Frequently asked

questions

Yes. The affected upload-resource API may be reachable remotely, and exploitation can occur when the deployment exposes the endpoint without effective authentication.

Not necessarily. The reported weakness is that the endpoint may accept requests without requiring valid authentication; network reachability and any deployment-level access controls remain relevant.

Require authentication and explicit authorization before processing uploads, then apply strict validation and least-privilege storage controls to the uploaded content.

Maintain an inventory of sensitive API routes, enforce authentication through secure-by-default middleware, test anonymous access in CI, and monitor policy exceptions and unexpected resource changes.

Find out what's already
exploitable in your codebase.