/

CVE-2026-85208

Severity:

HIGH RISK

(7.3)

Unrestricted Upload (CWE-434) in Medicine Order Controller

CVE-2026-85208

Deferred

Vulnerability type

Category:

Unrestricted File Upload

CWE:

CWE-284, CWE-434

Impact:

Potential remote code execution, server compromise, and unauthorized file placement

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

A vulnerability in the Order Management Controller of itsourcecode Online Medicine Delivery System 1.0 allows an attacker to upload files without adequate restrictions through the order creation function. Because the vulnerable endpoint may be remotely reachable, an attacker could place dangerous or unexpected files on the server when upload controls are insufficient.

Affected context

The issue occurs in the order management workflow at /rider/orders/controller.php?action=add, specifically in the doInsert function's handling of the image argument. It is relevant where the endpoint accepts remotely supplied files without consistently enforcing file type, content, naming, storage, and authorization controls.

Exploit preconditions

  • Attack surface: The remotely accessible order management endpoint
  • Required access: Ability to submit or reach the order creation request; authentication requirements depend on the deployment
  • Trigger point: Processing of the image argument by the doInsert function
  • Why exploitation is possible: The application permits file content to be stored without sufficiently restricting the accepted type, destination, or execution characteristics

Why this happens

The underlying bug is an unrestricted file upload caused by inadequate validation and authorization around user-controlled file data. Upload logic appears to treat the image parameter as trusted without reliably verifying its content, extension, destination, and non-executable storage context. This maps primarily to CWE-434, while CWE-284 is relevant where access-control checks do not sufficiently constrain who may invoke the upload operation.

Potential impact

  • An attacker may place unauthorized files on the application server.
  • A malicious file could enable code execution if stored in an executable location and interpreted by the server.
  • The application or host may be compromised.
  • Attackers could deface content, distribute malicious files, or affect service availability.
  • Stored files could consume disk space or expose sensitive information.

General mitigation guidance

Mitigation generally focuses on making uploads restrictive by default and

reducing trust in all client-provided metadata.

Common defensive patterns include:

  • Permit only the minimum required image formats using content inspection rather than filename checks alone.
  • Generate server-side filenames and store uploads outside executable web roots.
  • Enforce size, dimension, extension, and MIME-type limits consistently.
  • Apply authorization checks at the endpoint and object level before accepting uploads.
  • Serve uploaded content with non-executable response policies and appropriate content-disposition settings.
  • Use least-privilege service accounts and filesystem permissions for upload directories.
  • Reject ambiguous, malformed, or polyglot file content and avoid trusting client-supplied paths.

How teams detect issues like this

Detection approaches can include:

  • Static analysis rules for file-upload handlers that write request content directly to web-accessible or executable paths.
  • Code review checks for missing authorization, extension allowlists, content validation, generated filenames, and size limits.
  • Web-application testing that verifies rejected file types, altered MIME metadata, traversal-like names, and unauthorized requests without relying on weaponized payloads.
  • Runtime monitoring for unusual upload volumes, unexpected file extensions, executable content in upload directories, and requests to newly created files.
  • Policy enforcement requiring centralized upload components with safe storage defaults and security checks in CI pipelines.

Sources

SourceLink
github.comgithub.com/boyslikesports/202607_vul_dir/blob/main/H-12-FileUpload-RCE-RiderOrders_en.md
itsourcecode.comitsourcecode.com/
vuldb.comvuldb.com/cve/CVE-2026-85208
vuldb.comvuldb.com/submit/892999
vuldb.comvuldb.com/vuln/398416
vuldb.comvuldb.com/vuln/398416/cti

Frequently asked

questions

Yes, the issue is described as remotely exploitable when an attacker can reach

the order management endpoint and satisfy any deployment-specific access

requirements.

The available description does not establish whether authentication is

required. The important conditions are endpoint reachability and permission

to submit the affected order request.

Accept only required image formats, inspect file content, generate server-side

names, store files outside executable web paths, and enforce authorization

before processing the upload.

Use centralized, restrictive upload controls; apply least privilege to the

application and storage directories; review upload handlers for access-control

and validation gaps; and monitor uploaded content and directory activity.

Find out what's already
exploitable in your codebase.