/

CVE-2026-75339

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-862) in cjbi admin3 Storage

CVE-2026-75339

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized File Upload and Data Exposure

Severity:

HIGH RISK

(8.8)

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

cjbi admin3 v3.0.0 has missing permission checks on the /storage/upload endpoint. Any authenticated user may be able to upload arbitrary files, while anonymous users may be able to download stored files, creating risks of unauthorized content hosting, data exposure, and potentially broader application compromise depending on deployment behavior.

Affected context

The vulnerability occurs in the storage functionality of cjbi admin3 v3.0.0 when upload and download operations are reachable without appropriate authorization enforcement. Risk is greatest where uploaded files are stored in web-accessible locations, served with executable or active content types, or contain sensitive information.

Exploit preconditions

  • Attack surface: The /storage/upload endpoint and associated file-download functionality
  • Required access: A logged-in account for unauthorized uploads; anonymous network access may be sufficient for downloads
  • Trigger point: Sending an upload request or requesting a stored file
  • Why exploitation is possible: The affected operations do not consistently verify whether the caller is authorized to perform the requested action

Why this happens

The underlying issue is an authorization control failure mapped to CWE-862: Missing Authorization. The application exposes storage operations without enforcing an explicit permission decision for each request, allowing authentication status or direct endpoint reachability to substitute for resource and operation-level authorization.

Potential impact

  • An authenticated user may upload arbitrary files
  • Anonymous users could retrieve files that should be restricted
  • Attackers may host misleading, malicious, or unwanted content
  • Sensitive uploaded data may be disclosed
  • Stored active content could contribute to cross-site scripting or related attacks if served unsafely
  • Application or server compromise could occur if uploaded files are executed by the deployment

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every storage operation rather than relying on endpoint visibility or login status alone.

Common defensive patterns include:

  • Apply server-side, operation-level authorization checks to both upload and download requests
  • Use deny-by-default access policies and verify ownership or explicit sharing permissions
  • Keep uploaded files outside executable and publicly served directories where possible
  • Store files with non-executable permissions and serve them through controlled download handlers
  • Validate file type, size, and content independently of the filename or client-provided metadata
  • Use non-guessable object identifiers and avoid exposing storage paths
  • Run the storage service with the least privileges needed to access its data
  • Apply separate policies for anonymous access, authenticated access, and administrative operations

How teams detect issues like this

High-level detection can include:

  • Static analysis and code review checks for upload or download routes lacking authorization middleware
  • Review of controller and service methods to confirm authorization is enforced before storage access
  • Tests that exercise endpoints as anonymous users, ordinary users, and resource owners
  • Monitoring for unexpected upload volume, unusual file extensions, and anonymous download activity
  • Policy enforcement requiring authorization annotations or centralized access-control calls on storage operations
  • Automated application security testing that checks for unauthenticated file access and horizontal privilege violations

Sources

SourceLink
github.comgithub.com/fangtang7/CVE/blob/main/admin3/file.md

Frequently asked

questions

It may be exploitable over the network when the storage endpoints are exposed to an attacker. Upload abuse generally requires a valid login, while download exposure may be possible without authentication.

An account capable of reaching the upload endpoint may be sufficient for arbitrary uploads. Depending on deployment configuration, no account may be required to retrieve stored files.

Enforce explicit, server-side authorization for every upload and download operation, including ownership or permission checks for individual files.

Use centralized access-control enforcement, deny-by-default policies, authorization-focused tests, and secure storage isolation that prevents uploaded content from being executed or unintentionally exposed.

Find out what's already
exploitable in your codebase.