HomeWordPress vulnerabilitiesWooCommerce Stripe Payment Gateway
WooCommerce Stripe Payment Gateway vulnerabilities
WooCommerce Stripe Payment Gateway has 2 known vulnerabilities in this database. The most recent published record is dated 9 Nov 2026.
- Known vulnerabilities
- 2
- Active installs
- 700,000+
- Latest version
- 11.1.1
- Last updated
- 16 Oct 2026
- Most recent
- 9 Nov 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-123145 | Medium 4.4 | Before 11.1.0 | Fixed in 11.1.0 | 13 d ago |
| Broken access control CVE-2026-2381 | Medium 6.5 | Up to 10.7.0 | Fixed in a later version (latest 11.1.1) | 16 Jun 2026 |
Read the published descriptions
- CVE-2026-123145, 9 Nov 2026
- The WooCommerce Stripe Payment Gateway WordPress plugin before 11.1.0 does not exclude the account password from the checkout fields it saves to order metadata during express checkout, causing the password a customer chooses when creating an account at checkout to be stored in plaintext in the database, readable by anyone with access to order data or the database. Version 10.9.0 stored the passwords. Version 10.9.1 stopped new ones from being stored but left existing ones in place, and version 11.1.0 removes them on update. Passwords stored this way should be considered exposed. CVE record
- CVE-2026-2381, 16 Jun 2026
- The WooCommerce Stripe Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `ajax_pay_for_order()` function in all versions up to, and including, 10.7.0 This is due to a missing order ownership or order_key verification when processing payment for an order via the `wc_stripe_pay_for_order` WC-AJAX endpoint. The function only validates a nonce (which is publicly available on any WooCommerce page where Express Checkout is enabled), but does not verify that the requesting user owns the target order and is allowed to modify it. This makes it possible for unauthenticated attackers to force any pending order into a failed status by providing a fake payment method, causing a payment exception that updates the order status to "failed" via sequential order ID enumeration. CVE record
What to do if you run WooCommerce Stripe Payment Gateway
If you run WooCommerce Stripe Payment Gateway, 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 WooCommerce Stripe Payment Gateway vulnerabilities
Free. We email you when a new vulnerability is published for WooCommerce Stripe Payment Gateway, 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.