HomeWordPress vulnerabilitiesPayment Plugins for Stripe WooCommerce
Payment Plugins for Stripe WooCommerce vulnerabilities
Payment Plugins for Stripe WooCommerce has 3 known vulnerabilities in this database. The most recent published record is dated 9 Sep 2026.
- Known vulnerabilities
- 3
- Active installs
- 100,000+
- Latest version
- 4.0.16
- Last updated
- 24 Sep 2026
- Most recent
- 9 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 |
|---|---|---|---|---|
| Sensitive data exposure CVE-2026-80339 | Medium 5.3 | Before 4.0.12 | Fixed in 4.0.12 | 9 Sep 2026 |
| Broken access control CVE-2026-12654 | Medium 5.3 | Up to 4.0.7 | Fixed in a later version (latest 4.0.16) | 24 Jul 2026 |
| Broken access control CVE-2021-39347 | Medium 4.3 | Up to 3.3.9 | Fixed in a later version (latest 4.0.16) | 4 Oct 2021 |
Read the published descriptions
- CVE-2026-80339, 9 Sep 2026
- The Payment Plugins for Stripe WooCommerce WordPress plugin before 4.0.12 does not validate the order key before adding order data to the JavaScript configuration it outputs on the front end, allowing unauthenticated users to obtain the billing details of any order, together with the secret that gates access to it, by iterating sequential order identifiers. CVE record
- CVE-2026-12654, 24 Jul 2026
- The Payment Plugins for Stripe WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to mark arbitrary pending asynchronous WooCommerce orders as paid by forging a charge.pending event with attacker-controlled metadata.order_id, metadata.gateway_id, and a charge object carrying status=succeeded and captured=true, triggering payment_complete() and downstream fulfillment flows with an attacker-supplied transaction ID. Exploitation requires the merchant to have left the webhook_secret_test or webhook_secret_live option blank, which is the plugin's default state until a Stripe-issued whsec_ value is manually configured; once a non-empty secret is set, the signature verification cannot be bypassed. CVE record
- CVE-2021-39347, 4 Oct 2021
- The Stripe for WooCommerce WordPress plugin is missing a capability check on the save() function found in the ~/includes/admin/class-wc-stripe-admin-user-edit.php file that makes it possible for attackers to configure their account to use other site users unique STRIPE identifier and make purchases with their payment accounts. This affects versions 3.0.0 - 3.3.9. CVE record
What to do if you run Payment Plugins for Stripe WooCommerce
If you run Payment Plugins for Stripe 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 Plugins for Stripe WooCommerce vulnerabilities
Free. We email you when a new vulnerability is published for Payment Plugins for Stripe 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.