dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-45053

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
CubeCart is an ecommerce software solution. Prior to 6.7.0, an Authenticated Arbitrary File Upload vulnerability exists in the REST API File Manager endpoint (POST /api/v1/files) of CubeCart. The endpoint allows any holder of an API key with files:rw permission to upload PHP source files into the web-accessible images/source/ directory, where they are executed by the web server. Combined with a path-traversal flaw in the same endpoint's filepath parameter, a single API request writes a webshell anywhere the webserver process can write — including the document root — yielding full Remote Code Execution. This vulnerability is fixed in 6.7.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CubeCart versions before 6.7.0 contain an authenticated arbitrary file upload vulnerability in the REST API File Manager endpoint (POST /api/v1/files). Attackers with a valid API key possessing files:rw permission can upload PHP files to the web-accessible images/source/ directory where they execute, and combined with path traversal in the filepath parameter, can write webshells anywhere the web server process has write access, achieving full RCE.

MitigationUpgrade to CubeCart 6.7.0 or later. As a secondary measure, audit and rotate any API keys that were issued with files:rw permissions, and restrict API key access to only trusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check CubeCart version
    Locate the version file (typically includes/version.php or check the admin dashboard footer for version number) and compare it to 6.7.0
    Affected if Installed version is earlier than 6.7.0
  2. Verify REST API is enabled
    Check the CubeCart admin panel under Settings > API or inspect the configuration file (includes/config.php) for API enablement status
    Affected if REST API is enabled and accessible at /api/v1/
  3. Identify API keys with files:rw permission
    Query the database table containing API keys (commonly cubecart_api_keys or similar) or examine API key configuration in the admin panel to list keys and their assigned permissions
    Affected if Any API key exists with files:rw permission granted
  4. Confirm web accessibility of upload directory
    Check if the images/source/ directory exists within the web root and is accessible via HTTP (navigate to yourdomain.com/images/source/ or equivalent)
    Affected if The images/source/ directory exists and is web-accessible
  5. Audit for unauthorized PHP files in upload directories
    Search the web root for .php files in images/, upload/, and other writable directories, especially in images/source/
    Affected if Unexpected PHP files are found in web-accessible directories

You are affected if running CubeCart version below 6.7.0 with the REST API enabled and any API key possessing files:rw permission exists in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to CubeCart 6.7.0 or later. As a secondary measure, audit and rotate any API keys that were issued with files:rw permissions, and restrict API key access to only trusted users.

Recommended fix High confidence

6.7.0

  1. Backup the existing CubeCart installation and database before upgrading
  2. Download CubeCart version 6.7.0 or later from the official source
  3. Apply the upgrade to your existing CubeCart installation, following the standard upgrade procedure
  4. Verify the upgrade was successful by confirming the new version is running
  5. If using the REST API, ensure API keys with files:rw permission are reviewed and limited to trusted users only

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data