WooCommerce told stores using its Stripe Gateway on 11 November to update to 11.2.0, or 11.1.2 if they must stay on the 11.1.x branch. It says the most serious flaws “could allow for fraudulent purchases”.
WooCommerce’s advisory says it has “no evidence that these issues have been exploited”. It hasn’t said what they are or which earlier versions they affect. WordPress.org, which lists the plugin as WooCommerce Stripe Payment Gateway, puts it at 700,000+ active installations worldwide.
A separate password bug in version 10.9.0
The advisory also describes a bug in version 10.9.0 that could save a customer’s new account password in plain text in the store’s order data. It happened only when all of these applied:
- the store was on Stripe Gateway 10.9.0;
- it used the classic checkout and showed Stripe’s Express Checkout buttons on the checkout page;
- the shopper created an account with a password at checkout and paid with Apple Pay or Google Pay.
Store administrators and shop managers could see those passwords on the order screen, and so could tools that read order data, such as WP-CLI and the REST API. WooCommerce says it can’t tell whether anyone looked at them.
Version 10.9.1 stopped new passwords being saved this way. From 11.1.0, the plugin deletes any stored passwords from order records in the background after the update. If it finds and removes any, it shows a notice in the WordPress admin and emails the site administrator, with a count of accounts still using one of those passwords. It doesn’t reset anyone’s password.
Update, 17 November 2026, 07:32 GMT: The password bug has its own CVE number, CVE-2026-123145. The CVE record, published by WPScan on 9 November, lists versions 10.9.0 to 11.0.1 as affected. That range covers more than 10.9.0 because, the record says, 10.9.1 left already-stored passwords in place until 11.1.0 removed them. WooCommerce still hasn’t said what the fraudulent-purchase flaws are.
What to do
Go to Plugins, then Installed Plugins, in your WordPress admin and check the version of WooCommerce Stripe Gateway (also called Stripe for WooCommerce). WooCommerce says to check even if automatic updates are on or your host manages updates.
If it’s older than 11.2.0, select Update Now when WordPress offers 11.2.0 or later. Stores that must stay on 11.1.x can download 11.1.2 from the Previous Versions section of the WordPress.org plugin page and upload it, WooCommerce says. Then go back to Installed Plugins and check the version has changed.
Versions 11.2.0 and 11.1.2 need WordPress 6.9 and WooCommerce 11.0, so those may have to be updated first.
If your store matched all three conditions above, WooCommerce says to look for copies of the passwords in backups, order exports and any service that syncs your order data, even if you didn’t get the email. The clean-up only runs from 11.1.0, so copies made before then can still be in those places. It suggests asking affected customers to reset their store password and to change it anywhere else they used it.
If someone else looks after your store, ask them which plugin version you’re on, whether the store was ever on 10.9.0 with the classic checkout and Apple Pay or Google Pay buttons, and whether your backups and order exports have been checked for stored passwords.
Developers and agencies should check every store they look after, including staging and development copies that can be reached from the internet, WooCommerce says.
What isn’t known
WooCommerce hasn’t said what the fraudulent-purchase flaws are, which earlier versions they affect or whether they have CVE numbers. WordPress.org gives only a worldwide install figure, so it isn’t known how many UK stores use the plugin.
Alex De Sousa is the founder of Digital Royalty, a software development company in Portsmouth that builds websites, web apps and AI tools for UK businesses.