HomeWordPress vulnerabilitiesPayment Gateway of Stripe for WooCommerce
Payment Gateway of Stripe for WooCommerce vulnerabilities
Payment Gateway of Stripe for WooCommerce has 2 known vulnerabilities in this database. The most recent published record is dated 19 Sep 2026.
- Known vulnerabilities
- 2
- Active installs
- 7,000+
- Latest version
- 5.1.0
- Last updated
- 1 Sep 2026
- Most recent
- 19 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Security weakness CVE-2026-9832 | Medium 5.3 | Up to 5.0.8 | Fixed in a later version (latest 5.1.0) | 19 Sep 2026 |
| Authentication bypass CVE-2023-3162 | Critical 9.8 | Up to 3.7.7 | Fixed in a later version (latest 5.1.0) | 31 Aug 2023 |
Read the published descriptions
- CVE-2026-9832, 19 Sep 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 `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 record
- CVE-2023-3162, 31 Aug 2023
- The Stripe Payment Plugin for WooCommerce plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 3.7.7. This is due to insufficient verification on the user being supplied during a Stripe checkout through the plugin. This allows unauthenticated attackers to log in as users who have orders, who are typically customers. CVE record
What to do if you run Payment Gateway of Stripe for WooCommerce
If you run Payment Gateway of Stripe for WooCommerce, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Payment Gateway of Stripe for WooCommerce vulnerabilities
Free. We email you when a new vulnerability is published for Payment Gateway of Stripe for WooCommerce, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.