# CVE-2026-92400: Business logic in Payment Gateway for PayPal on WooCommerce

> Unauthenticated attackers can mark orders as paid by exploiting sandbox IPN environment confusion, bypassing payment verification in the WooCommerce PayPal plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-p33j-7gxx-7v4f

## What is CVE-2026-92400?

CVE-2026-92400 is a medium-severity vulnerability in Unknown Payment Gateway for PayPal on WooCommerce, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Payment Gateway for PayPal on WooCommerce WordPress plugin before 9.2.1 does not verify that an incoming payment notification was confirmed in the store's configured payment environment or paid to the store's own merchant account before marking an order complete, allowing unauthenticated users to mark their own orders as paid using a genuine transaction from a payment sandbox they control.

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

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


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

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

## Is CVE-2026-92400 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92400 is a medium-severity vulnerability in Unknown Payment Gateway for PayPal on WooCommerce, published on 21 Sep 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-92400 in the wild and no public exploit code.

Affected product: Unknown Payment Gateway for PayPal on 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-92400/ (Markdown: https://insights.sbomify.com/CVE-2026-92400/index.md)
```

## Sources

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

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