Black Friday lands on November 27. That gives most WooCommerce store owners about a week to make sure their checkout is safe before the busiest traffic of the year hits it.
In the last few weeks, WooCommerce has shipped security fixes for two of its most popular payment plugins. PHP itself pushed out critical patches in October. None of this made the evening news, but every one of these updates touches the part of your store that takes money.
I have spent this week walking our WooCommerce clients through the same checklist. Here is what changed, what it means for your store, and the exact order I would handle it in.
What Changed in November
The Stripe Gateway password bug
On November 11, WooCommerce published an advisory for the WooCommerce Stripe Gateway plugin. Version 10.9.0 had a bug that saved customer account passwords in plain text inside order data. It hit stores using classic checkout with Stripe Express Checkout buttons, where a shopper created an account at checkout and paid with Apple Pay or Google Pay.
Those passwords were visible to admins and shop managers in the order screen, through WP-CLI, and through the REST API. The fix lives in version 11.2.0, or 11.1.2 if you need to stay on the 11.1 branch. WooCommerce says the update also closes other issues, and the most serious ones “could allow for fraudulent purchases.” They report no evidence of exploitation so far.
The public CVE record (CVE-2026-123145) scores the password exposure at 4.4, which is medium. Do not let that number relax you. A medium score on a payment plugin during your highest volume week is still a real problem.
The WooPayments subscriptions fix
On November 3, WooCommerce released patched versions of WooPayments for a security issue in its bundled subscriptions feature. They shipped a fixed release for almost every version line going back to 9.0. If you run anything older than 9.0.0, the advice is to jump straight to 11.2.1.
The PHP patches most store owners missed
On October 21, the PHP team released fixes for two critical flaws scored 9.2 out of 10. They can let an attacker run code on your server without logging in. The patched versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
Here is the catch. Updating WordPress or WooCommerce does nothing for this. The fix happens at the server level, which means your host or your developer has to do it.
What the Top Articles Leave Out
I read through the official advisories and the coverage ranking for these updates. They do a good job of listing version numbers. What they skip is the part that trips up real businesses, which is who owns the update.
In many of the stores we audit, nobody does. The owner thinks the host handles it. The host thinks the freelancer handles it. The freelancer finished the project two years ago. Meanwhile, auto-updates quietly fail because the newest Stripe plugin needs WordPress 6.9 and WooCommerce 11.0, and the site is still on older versions.
WooCommerce itself tells merchants to check the installed version even when auto-updates are on. That one line tells you how often “automatic” falls short in practice.
My Seven Step Security Checklist Before Black Friday
This is the order I use with clients. Block out two hours this week and work through it.
- Take a full backup first. Save files and the database somewhere other than your hosting account. Never update a payment plugin without a way back.
- Check your PHP version. Go to Tools, then Site Health, then Info, then Server. If it is below the patched versions listed above, message your host today and ask them to confirm the patch is running, not just scheduled.
- Check WordPress and WooCommerce core. The latest Stripe plugin needs WordPress 6.9 and WooCommerce 11.0. If you are behind, update core first or the plugin update will fail.
- Update Stripe Gateway and WooPayments. Go to Plugins, then Installed Plugins, and confirm the version numbers with your own eyes after updating.
- Test checkout on staging, then live. Run a real order with a card, with Apple Pay or Google Pay, and with a coupon. Refund it afterward.
- Look for leftover passwords. If you ran Stripe 10.9.0 with Express Checkout, check backups, order exports and sync tools like your CRM or accounting app. The plugin cleans its own database, but it cannot clean copies sitting elsewhere.
- Write down what you checked. Record version numbers, dates and who did the work. If you manage several sites, include staging and development copies too.
A Scenario We See Every November
Picture a home goods store that makes a big share of its yearly revenue between late November and December. The site looks fine. Orders are coming in. Nobody has a reason to worry.
Then we check. The store is on Stripe Gateway 10.9.0 with Express Checkout buttons switched on. The server runs PHP 8.0, and WooCommerce is two major versions behind, which is why every plugin auto-update has failed for months without anyone noticing. The host assumed the agency handled updates. The agency stopped working with them in spring.
The fix is not dramatic. We move the site to PHP 8.3 on staging, update core, then the payment plugins, and run test orders across every payment method. If the plugin reports customers with stored passwords, we draft a short, honest email asking them to reset it. That is one afternoon of work. The alternative is walking into Black Friday with an exposed checkout and no idea who is responsible for it.
Put the PHP Deadlines on Your Calendar
Two more dates matter. PHP 8.2 reaches end of life on December 31, 2026, so stores on 8.2 stop getting security fixes after that. WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer.
WooCommerce’s own data shows about 7% of tracked stores still run PHP 7.4 and about 2% run PHP 8.0. If you are in that group, plan the move to PHP 8.3 now, test it once the holiday rush settles, and stop carrying that risk into 2027.
The Takeaway
Your checkout is the one part of your store you cannot afford to guess about this month. Back it up, check the versions yourself, test a real order, and decide in writing who owns updates from here on.
If you need a hand executing this, whether building or fixing a Shopify or WooCommerce store, developing a custom app, or getting unstuck with ads and SEO, you can reach out to our team at ConceptRecall (conceptrecall.com) for an honest conversation. No pressure, just a clear look at where your store stands.
Frequently Asked Questions
Does updating WooCommerce fix the October PHP vulnerabilities?
No. The PHP flaws sit in the server software, not in WordPress or WooCommerce. Your host or developer needs to install the patched PHP version. Some managed platforms, such as WordPress.com and Pressable, have already handled it.
Do I need to reset customer passwords after the Stripe Gateway fix?
Only if your store ran version 10.9.0 with Express Checkout on classic checkout. The plugin removes stored passwords but does not reset them, so asking affected customers to change their password is the safe move.
Is it safe to update plugins right before Black Friday?
Yes, if you back up first and test checkout afterward. Running a known vulnerable payment plugin during peak traffic carries far more risk than a tested update.