# CVE-2026-87860: Subscriptions for WooCommerce < 2.0.3 - Subscription Cancellation via CSRF

> Attackers can trick logged-in customers into canceling their own active subscriptions via a crafted request due to missing CSRF protection.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A: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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-4q57-7phr-hqc4

## What is CVE-2026-87860?

CVE-2026-87860 is a medium-severity vulnerability in Unknown Subscriptions for WooCommerce, published on 16 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

The Subscriptions for WooCommerce WordPress plugin before 2.0.3 does not verify the security token on the request that cancels a subscription, allowing attackers to make a logged-in customer cancel their own active subscription through a crafted request they are tricked into making.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-87860 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87860 is a medium-severity vulnerability in Unknown Subscriptions for WooCommerce, published on 16 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-87860 in the wild and no public exploit code.

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

## Sources

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

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