# CVE-2026-9832: Security feature bypass in Payment Gateway of Stripe for WooCommerce

> Unauthenticated attackers can forge Stripe webhook events to manipulate order statuses if the webhook signing secret is not configured.

- **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:** 19 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-7cxm-23jc-4x3x

## What is CVE-2026-9832?

CVE-2026-9832 is a medium-severity vulnerability in themehigh Payment Gateway of Stripe for WooCommerce, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Payment Gateway of Stripe for WooCommerce plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in all versions up to, and including, 5.0.8. This is due to the publicly accessible `woocommerce_api_wt_stripe` webhook endpoint (`EH_Stripe_Webhook_Handler::handle()`) wrapping the only call to `\Stripe\Webhook::constructEvent()` inside an `if (!empty($endpoint_secret))` guard that is never entered on default installations — because the `eh_stripe_webhook_secret` option is empty after a fresh plugin install — causing the raw, attacker-controlled POST body to be decoded and processed as a fully trusted Stripe event without any signature verification, authentication, or authorization. This makes it possible for unauthenticated attackers to send forged Stripe webhook events to manipulate WooCommerce order statuses, including marking unpaid orders as paid or completed via `payment_complete()`, forcing legitimate orders into a failed state, fabricating dispute notifications, and injecting forged refund events. This vulnerability is only exploitable when the Stripe webhook signing secret has not been configured by an administrator; once a valid signing secret is saved, `\Stripe\Webhook::constructEvent()` is enforced and forged requests are rejected.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-9832 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9832 is a medium-severity vulnerability in themehigh Payment Gateway of Stripe for WooCommerce, published on 19 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-9832 in the wild and no public exploit code.

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

## Sources

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

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