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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Sources
Also known as GHSA-7cxm-23jc-4x3x.