# CVE-2026-15211: Subscriptions for WooCommerce < 2.0.1 - Payment Bypass via Attacker-Supplied PayPal Capture Token

> Attackers can bypass payment validation in Subscriptions for WooCommerce by supplying a valid PayPal token, marking expensive orders as paid without payment.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-p384-7c3j-gqm7

## What is CVE-2026-15211?

CVE-2026-15211 is a medium-severity vulnerability in Unknown Subscriptions for WooCommerce, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Subscriptions for WooCommerce WordPress plugin before 2.0.1 does not validate the payment amount or bind the PayPal order token to the order being completed on the WooCommerce order-received flow: it captures a client-supplied token and marks the order paid whenever the capture status is COMPLETED, without comparing the captured amount to the order total. This allows an attacker (unauthenticated where guest checkout is enabled) to substitute an approved, uncaptured PayPal order token and have an expensive order marked paid without paying its price.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-15211 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15211 is a medium-severity vulnerability in Unknown Subscriptions for WooCommerce, published on 7 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-15211 exists.

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

## Sources

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

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