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.
CVE-2026-9832
MEDIUMPre-NVD 5.35.3—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.3 from GitHub Security Advisory published 2026-09-19. a secondary CVSS source baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 19, 2026
Last Modified
September 19, 2026
References (10)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L18
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L321
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L66
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L93
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L18
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L321
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L66
- security@wordfencehttps://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L93
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3575195%40payment-gateway-stripe-and-woocommerce-integration&new=3575195%40payment-gateway-stripe-and-woocommerce-integration
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/2cef154c-efb8-4455-9be6-e3cf8b95e9d3?source=cve
Vendor Advisories for CVE-2026-9832(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 14:26 UTCEG score recompute
- 2026-09-19 14:26 UTCGHSA enrichment
- 2026-09-19 14:10 UTCEG score recompute
- 2026-09-19 14:10 UTCGHSA enrichment
- 2026-09-19 08:18 UTCEG score recompute
- 2026-09-19 07:51 UTCEG score recompute
- 2026-09-19 07:50 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-9832?
CVE-2026-9832 is a medium vulnerability published on September 19, 2026. 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 woocommerceapiwtstripe webhook endpoint (EHStripeWebhookHandler::handle())…
When was CVE-2026-9832 disclosed?
CVE-2026-9832 was first published in the National Vulnerability Database on September 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9832 actively exploited?
CVE-2026-9832 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.4% of all scored CVEs.
What is the CVSS score of CVE-2026-9832?
CVE-2026-9832 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-9832?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9832, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9832
Is Your Infrastructure Affected by CVE-2026-9832?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.