Order-status manipulation via unsigned Stripe webhooks
Published Sep 19, 2026 · Updated Sep 19, 2026
Improper signature verification in ThemeHigh Payment Gateway of Stripe for WooCommerce 5.0.8 and earlier allows remote attackers to alter order states. EH_Stripe_Webhook_Handler::handle() decodes and trusts the raw POST body when eh_stripe_webhook_secret is empty, bypassing Stripe\Webhook::constructEvent(). Exploitation requires an unset signing secret and permits forged payment, failure, dispute, and refund events without authentication.
Summary
What happened
Improper signature verification in ThemeHigh Payment Gateway of Stripe for WooCommerce 5.0.8 and earlier allows remote attackers to alter order states. EH_Stripe_Webhook_Handler::handle() decodes and trusts the raw POST body when eh_stripe_webhook_secret is empty, bypassing Stripe\Webhook::constructEvent(). Exploitation requires an unset signing secret and permits forged payment, failure, dispute, and refund events without authentication.
The record
- CVE
- CVE-2026-9832
- Published
- Sep 19, 2026
- Updated
- Sep 19, 2026
- Vendor
- ThemeHigh
- Product
- Payment Gateway of Stripe for WooCommerce
- Classifications
- CWE-347, T1565.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2026CVE publishedPublication date reported by the CVE source.
- Sep 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=5.0.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started