# CVE-2026-45053: CubeCart: Authenticated Arbitrary File Upload to RCE in REST Files API

> Authenticated attackers with API access can upload malicious PHP files to achieve remote code execution on CubeCart installations.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-652f-8c88-25cx

## What is CVE-2026-45053?

CVE-2026-45053 is a critical vulnerability in cubecart v6, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-45053?


## How do I fix CVE-2026-45053?

No fix has been published for CVE-2026-45053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45053 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45053 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45053 and fix it if it is affected.

What it is: CVE-2026-45053 is a critical vulnerability in cubecart v6, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45053 exists.

Affected product: cubecart v6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45053/ (Markdown: https://insights.sbomify.com/CVE-2026-45053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45053
- OSV: https://osv.dev/vulnerability/CVE-2026-45053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45053/
Summaries are generated and may contain mistakes; the official description above is the record.