# CVE-2026-54648: CubeCart: Missing Authorization Check in customers.gdpr.inc.php Leads to Unauthorized Customer Data Deletion

> Authenticated administrators with read-only privileges can bypass authorization checks to irreversibly delete customer records and guest accounts in CubeCart.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-r376-2wr5-g9qx

## What is CVE-2026-54648?

CVE-2026-54648 is a medium-severity missing authorization vulnerability in cubecart v6, published on 17 Sep 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.5, the GDPR tools in admin/sources/customers.gdpr.inc.php rely on page-level CC_PERM_READ access and do not require CC_PERM_DELETE for the purge, no_order_purge, or delete_guests commands. An authenticated administrator with read-only customer privileges can invoke these backend actions directly to bypass interface restrictions and irreversibly delete customer records, accounts without orders, or guest accounts, compromising data integrity and availability. This issue is fixed in version 6.7.5.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-54648 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54648 is a medium-severity missing authorization vulnerability in cubecart v6, published on 17 Sep 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-54648 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-54648/ (Markdown: https://insights.sbomify.com/CVE-2026-54648/index.md)
```

## Sources

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

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