# CVE-2026-54642: CubeCart: CSRF Protection Missing for Download Resets and Card Deletions in orders.index.inc.php

> An attacker can trick an authenticated CubeCart administrator into resetting download counters or deleting stored payment cards via CSRF.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-cq6g-rf5m-42xg

## What is CVE-2026-54642?

CVE-2026-54642 is a medium-severity vulnerability in cubecart v6, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

CubeCart is an ecommerce software solution. Prior to 6.7.5, the reset_id download-counter action and delete_card stored-payment-card action in admin/sources/orders.index.inc.php use state-changing GET requests and are omitted from the protection map in admin/skins/default/csrf.inc.php. A remote attacker can induce an authenticated administrator to issue one of these requests without a validated session token, causing unintended resets of electronic download usage counters or deletion of stored customer payment-card tokens. This issue is fixed in version 6.7.5.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-54642 being exploited?

There is no known exploitation of CVE-2026-54642 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54642 is a medium-severity vulnerability in cubecart v6, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54642 in the wild and no public exploit code.

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-54642/ (Markdown: https://insights.sbomify.com/CVE-2026-54642/index.md)
```

## Sources

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

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