# CVE-2026-10524: CoCart < 4.9.0 - Unauthenticated Arbitrary Price Manipulation

> Unauthenticated attackers can manipulate product prices via REST API to complete orders at arbitrary totals, affecting WooCommerce stores using CoCart.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-2xcr-jvj8-gv2p

## What is CVE-2026-10524?

CVE-2026-10524 is a high-severity vulnerability in Unknown CoCart, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CoCart WordPress plugin before 4.9.0 does not validate a user-supplied price value against the actual product price when items are added to the cart through one of its public REST API endpoints, allowing unauthenticated users to set arbitrary product prices and complete WooCommerce orders at manipulated totals.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2026-10524 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10524 is a high-severity vulnerability in Unknown CoCart, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10524 exists.

Affected product: Unknown CoCart. 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-10524/ (Markdown: https://insights.sbomify.com/CVE-2026-10524/index.md)
```

## Sources

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

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