# CVE-2026-15045: Wallet System for WooCommerce < 2.7.10 - Customer+ Checkout Price Manipulation via Unvalidated Wallet Amount

> Authenticated customers can manipulate wallet amounts to reduce order totals to zero, bypassing payment requirements in the Wallet System for WooCommerce plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-gf9j-rpmq-8vq3

## What is CVE-2026-15045?

CVE-2026-15045 is a medium-severity vulnerability in Unknown Wallet System for WooCommerce, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Wallet System for WooCommerce WordPress plugin before 2.7.10 does not validate a user-supplied wallet amount against the customer's actual stored balance during checkout, allowing authenticated customers to arbitrarily reduce their own order total, including down to zero, and complete checkout without paying the merchant.

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

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


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

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

## Is CVE-2026-15045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15045 is a medium-severity vulnerability in Unknown Wallet System for WooCommerce, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15045 in the wild and no public exploit code.

Affected product: Unknown Wallet System for WooCommerce. 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-15045/ (Markdown: https://insights.sbomify.com/CVE-2026-15045/index.md)
```

## Sources

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

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