Skip to content
WooCommerce

WooCommerce Stripe Plugin Security Fix: Update to 11.2.0 or 11.1.2

WooCommerce asks every store using its Stripe gateway to update to 11.2.0 or 11.1.2. Who is affected by the stored password bug, what to update and what to check after.

Harsh PrajapatiFull stack developer
Published
Reading time
8 min
<??>

WooCommerce Stripe Plugin Security Fix: Update to 11.2.0 or 11.1.2

If your WooCommerce store takes payments through the WooCommerce Stripe Payment Gateway plugin, update it now to version 11.2.0, or to 11.1.2 if you need to stay on the 11.1 line. WooCommerce published a security advisory on 11 November 2026 covering several fixes, including a bug in version 10.9.0 that could save a customer's new account password in plain text inside the order data. WooCommerce says it has no evidence that these issues were exploited, so this is a data exposure to clean up, not a reported hack.

This guide is for store owners and the people who run stores for them. It covers who is affected, what to update, what to check once the update is done, what not to do, and how to fit this into the week before Black Friday.

What WooCommerce announced

The advisory, Security fix for WooCommerce Stripe Gateway (opens in a new tab), was posted on the WooCommerce Developer Blog on 11 November 2026. It says Automattic found several security issues in the Stripe gateway through its own internal scanning and fixed them in two releases: 11.2.0, and 11.1.2 for stores that need to stay on the 11.1 branch.

Most of these issues are described only in general terms. The advisory says the most significant of them could allow fraudulent purchases, and that there is no evidence any of them were exploited. The one issue it explains in detail is the stored password bug, and it is the one store owners need to act on. The advisory does not list a CVE number.

Is your store affected?

Every store running the WooCommerce Stripe Payment Gateway should update, because the fraud-related fixes apply to the plugin generally. The stored password bug is narrower, and it only touched stores that met all of these conditions:

ConditionWhat it means for your store
Plugin version 10.9.0The store ran 10.9.0 at some point. According to the advisory, 10.9.1 stopped new passwords being stored
Classic checkoutThe store used the classic (shortcode) checkout, not the Checkout block
Express Checkout on the checkout pageStripe's Express Checkout buttons showed on the checkout page
Account created at checkoutThe shopper set a password to create an account while ordering
Apple Pay or Google PayThe shopper paid with one of those wallets

If a shopper did all of that, their new password could be saved in plain text in the order data, where administrators, shop managers and tools that read order metadata, such as WP-CLI and the REST API, could see it. WooCommerce says it is not known whether anyone actually looked. Stores outside these conditions still need the update for the other fixes.

Which versions fix it

The fixed versions are 11.2.0 and 11.1.2. The plugin page on WordPress.org (opens in a new tab) shows 11.2.0 as the current version, requiring WordPress 6.9 or newer and PHP 7.4 or newer. The advisory adds that both fixed versions need WooCommerce 11.0, so an older store may have to update WordPress and WooCommerce before the Stripe plugin will move.

Current fixed version of the Stripe gateway
11.2.0
Fixed version for stores staying on 11.1.x
11.1.2
Minimum WordPress version for both fixes
6.9
Minimum WooCommerce version for both fixes
11.0

If WooCommerce itself is behind, read what changed in WooCommerce 11 before you jump several versions, because each 11.x release includes a database update.

What to do now

Update first, then check. The update stops the problem and starts the clean-up, and the checks deal with what was already copied elsewhere.

  1. Back up the store
  2. Update to 11.2.0 or 11.1.2
  3. Confirm the version
  4. Test a Stripe payment
  5. Check copies of order data
  1. Take a backup you can restore. WooCommerce's own guide to updating (opens in a new tab) says to back up and test on staging where possible, and to update sooner than usual when a release includes a security fix.
  2. Update the Stripe gateway to 11.2.0, or 11.1.2 if you must stay on 11.1.x. If WordPress or WooCommerce are too old, update those first.
  3. Confirm the installed version under Plugins, then Installed Plugins. The advisory asks you to check this even if automatic updates are switched on.
  4. Place a real test order with a card and, if you offer them, Apple Pay or Google Pay. A checkout that fails in sale week loses orders, so test before moving on.
  5. Repeat on every site you run, including staging and development copies, and note the versions you checked. If a host or developer manages your updates, ask them to confirm in writing.

What to check after updating

The update removes passwords from your live orders, but not from copies made before it. From version 11.1.0, the plugin clears previously stored passwords from order records in the background after the update. If it finds and removes any, it shows an admin notice and emails the site administrator, and the email gives a count of accounts that still use a password it found.

The clean-up does not change or reset any customer's password. It also cannot reach anything outside your live database. The advisory asks you to look for stored passwords in these places, even if you got no email:

  • Backups. Database backups taken while 10.9.0 was running may hold the passwords. Decide how long you really need those backups and who can open them.
  • Order exports. CSV or spreadsheet exports of order data, including ones sent to an accountant or a fulfilment partner.
  • Services that sync orders. Accounting, CRM, shipping or marketing tools that copy order metadata out of WooCommerce.

Then look at who can see order data at all. Every administrator and shop manager account could have seen these passwords, so this is a good moment to remove old staff accounts and agency logins you no longer use.

Should customers reset their passwords?

WooCommerce's advice is to consider asking affected customers to reset their store password and to change it anywhere else they used the same one. The admin email count tells you whether any accounts still use an exposed password. If that count is zero, no store account still uses an exposed password, but customers may have reused it elsewhere, so a short note is still worth considering.

For stores in India, customer passwords may count as personal data. India's Digital Personal Data Protection (DPDP) Act sets duties around protecting it, and it is worth getting proper advice on what applies to your store.

What not to do

Do not treat this as a hacked site. WooCommerce reports no evidence of exploitation, and wiping the store or restoring an old backup would cost you orders and could bring back the very data the update removes.

  • Do not roll back to an older Stripe version to "be safe". Older versions lack the fixes.
  • Do not force a password reset on every customer before you have read the admin email count. WooCommerce suggests considering resets for affected customers, not all of them.
  • Do not edit the database by hand to delete order metadata. The plugin's background clean-up is built for this.
  • Do not assume auto updates did the job. Check the version on each site yourself.

If you see signs of a wider problem, such as unknown admin users, odd redirects or injected scripts, that is a separate issue, and our hacked WordPress site clean-up guide covers what to do.

How this fits Black Friday week

Make this update now, not after the sale. Black Friday falls on 27 November 2026, and many stores freeze changes in the days before it. A security update is the exception, and the advisory notes that WooCommerce shipped fixes on two branches so stores can stay stable heading into the end-of-year period.

Update on a quiet day this week, test a payment with every method you offer, then keep the freeze. If WordPress or WooCommerce also need updating first, that is a bigger job, so start it today. A regular WooCommerce store maintenance plan helps keep stores close to current, so fixes like this are less work.

Do it yourself or get help?

A store already on WooCommerce 11 and WordPress 6.9 or newer, with a standard Stripe setup, can usually be updated by its owner, followed by a test order. Get help when the store is several versions behind, when checkout has custom code or extra payment plugins, or when you run several stores and need a written record of what was checked.

Our WooCommerce development work covers bringing older stores up to current WordPress and WooCommerce versions, WooCommerce checkout and payment gateway setup covers updating and testing Stripe safely, and website maintenance and support covers keeping every store current.

Frequently asked questions

Was my WooCommerce store hacked?

Not because of this advisory. WooCommerce says it has no evidence the issues were exploited. The password bug was a data exposure inside your own order records, visible to people and tools with access to order data.

Does updating delete the stored passwords?

From version 11.1.0, the plugin removes previously stored passwords from order records in the background and emails the site administrator if it finds any. It does not touch backups, order exports or services that already copied your order data.

I use WooPayments, not the Stripe plugin. Am I affected?

This advisory is about the WooCommerce Stripe Payment Gateway plugin. WooPayments is a separate plugin, and WooCommerce published its own security update for it on 3 November 2026, so update that as well.

Why will the Stripe plugin not update on my site?

Versions 11.2.0 and 11.1.2 require WordPress 6.9 and WooCommerce 11.0. If your site is older, update WordPress and WooCommerce first, ideally on a staging copy, then update the Stripe plugin.

Sources

The facts in this article were checked against these pages, last reviewed 18 November 2026.

  1. Security fix for WooCommerce Stripe Gateway: update to 11.2.0 or 11.1.2, WooCommerce Developer Blogdeveloper.woocommerce.com/2026/11/11/stripe-gateway-security-update/
  2. WooCommerce Stripe Payment Gateway, WordPress.org Plugin Directorywordpress.org/plugins/woocommerce-gateway-stripe/
  3. How to update WooCommerce, WooCommerce Documentationwoocommerce.com/document/how-to-update-woocommerce/
  4. Security update for WooPayments, WooCommerce Developer Blogdeveloper.woocommerce.com/2026/11/03/security-update-for-woopayments/
Harsh Prajapati, the author

Written by

Harsh Prajapati

Freelance full stack developer, founder of Worklancio

Web developer since 2018, freelancing since 2022. Builds WordPress sites and plugins, web apps and CRMs from Ahmedabad.

You may also like