/

CVE-2026-86666

Severity:

HIGH RISK

(7.3)

Unrestricted File Upload (CWE-434) in iWebShop-5 5.15

CVE-2026-86666

Deferred

Vulnerability type

Category:

Unrestricted File Upload

CWE:

CWE-284, CWE-434

Impact:

Unauthorized File Placement and Potential Remote Code Execution

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 remotely reachable unrestricted file upload flaw in iWebShop-5 affects the upload_json and uploadFile functionality in controllers/pic.php. If an attacker can reach the upload endpoint and the application does not sufficiently restrict uploaded content, they may place unauthorized files on the server, potentially enabling further compromise.

Affected context

The issue occurs in iWebShop-5 deployments using the image or file upload functionality implemented by controllers/pic.php. Risk depends on whether the affected endpoints are remotely accessible, whether authentication or authorization is enforced, how uploaded content is validated and stored, and whether the destination permits uploaded files to be interpreted or executed.

Exploit preconditions

  • Attack surface: Remotely accessible upload functionality
  • Required access: Access sufficient to submit requests to the affected upload endpoint; the exact requirement depends on deployment authentication and authorization
  • Trigger point: Processing of requests handled by upload_json or uploadFile
  • Why exploitation is possible: Inadequate restrictions may allow attacker-controlled files or file types to be accepted and stored without effective content, filename, or destination controls

Why this happens

The underlying bug is an unrestricted file upload condition, mapped primarily to CWE-434: Unrestricted Upload of File with Dangerous Type. The application appears to rely on insufficient validation or authorization around uploaded content, allowing user-controlled files to pass through the upload workflow. CWE-284: Improper Access Control may also apply when access to the upload operation or its stored files is not constrained according to the caller's privileges.

Potential impact

  • An attacker may store unauthorized files on the application server.
  • Uploaded content could be used to deface the application or distribute malicious material.
  • If the server interprets uploaded files as executable content, the attacker could gain code execution.
  • The application or host could be exposed to further compromise, data loss, or service disruption.

General mitigation guidance

Mitigation generally focuses on reducing trust in uploaded content and separating file storage from executable application paths.

Common defensive patterns include:

  • Allowing only narrowly defined business-required file types and validating content independently of the filename or client-provided MIME type.
  • Generating server-side filenames and storing uploads outside web-accessible or executable directories.
  • Enforcing authorization, request-size limits, quotas, and rate controls for upload operations.
  • Disabling script execution and dangerous handler mappings in upload locations.
  • Applying least-privilege permissions to the application account and uploaded files.
  • Serving uploaded content with restrictive response headers and preventing unintended content interpretation.
  • Using secure-by-default upload libraries and rejecting files that cannot be validated against an explicit schema.

How teams detect issues like this

Detection approaches can include:

  • Static analysis for upload handlers that trust client-supplied filenames, extensions, MIME types, or paths.
  • Code review checks for missing authorization, weak allowlists, direct use of upload names, and storage beneath executable web directories.
  • Web application testing that verifies rejected file types, content mismatches, oversized requests, and unauthorized upload attempts without retaining harmful files.
  • Monitoring upload endpoints for anomalous volume, unusual extensions, executable content signatures, unexpected destination paths, and subsequent requests for newly created files.
  • Policy enforcement requiring centralized upload validation and isolated storage across application components.

Sources

SourceLink
github.comgithub.com/aircheng-org/iWebShop-5/
github.comgithub.com/aircheng-org/iWebShop-5/issues/3
vuldb.comvuldb.com/cve/CVE-2026-86666
vuldb.comvuldb.com/submit/908924
vuldb.comvuldb.com/vuln/399757
vuldb.comvuldb.com/vuln/399757/cti

Frequently asked

questions

Yes, the affected upload functionality is described as remotely reachable. Practical exploitability still depends on endpoint exposure, authentication, authorization, and server configuration.

Not necessarily. The required access depends on how the upload endpoints are protected in a particular deployment; an account or valid session may be required where access controls are present.

Enforce authorization and strict server-side file validation, generate safe filenames, and store uploads in a non-executable location outside the web root.

Use centralized, secure-by-default upload handling; apply allowlists and content inspection; isolate uploaded files; enforce least privilege; and monitor upload activity and access to newly stored files.

Find out what's already
exploitable in your codebase.