# CVE-2026-2381: Missing authorization in WooCommerce Stripe Payment Gateway

> Unauthenticated attackers can manipulate order statuses to failed by exploiting missing ownership checks in the Stripe payment gateway plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-xpf8-p6c2-qcp9

## What is CVE-2026-2381?

CVE-2026-2381 is a medium-severity missing authorization vulnerability in WooCommerce Stripe Payment Gateway, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WooCommerce Stripe Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `ajax_pay_for_order()` function in all versions up to, and including, 10.7.0 This is due to a missing order ownership or order_key verification when processing payment for an order via the `wc_stripe_pay_for_order` WC-AJAX endpoint. The function only validates a nonce (which is publicly available on any WooCommerce page where Express Checkout is enabled), but does not verify that the requesting user owns the target order and is allowed to modify it. This makes it possible for unauthenticated attackers to force any pending order into a failed status by providing a fake payment method, causing a payment exception that updates the order status to "failed" via sequential order ID enumeration.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-2381 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2381 is a medium-severity missing authorization vulnerability in WooCommerce Stripe Payment Gateway, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2381 in the wild and no public exploit code.

Affected product: WooCommerce Stripe Payment Gateway. 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-2381/ (Markdown: https://insights.sbomify.com/CVE-2026-2381/index.md)
```

## Sources

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

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