Black Friday: 7 Last-Minute Checks for Your WooCommerce Store
Black Friday is days away. Here are the 7 checks we run on every WooCommerce store before Friday, plus what you shouldn't touch this week.
Read more →WooCommerce 11.2.2 shipped on November 4, 2026 as a security release. Here's what it fixes, what changes in your store, and a step-by-step way to update without losing orders.
The short version: WooCommerce 11.2.2 came out on November 4, 2026. It’s a security release, and WooCommerce recommends installing it as soon as possible. There are no new features. It hardens checkout, the REST API, and the admin, and it includes a database update. Below we cover what changed, two behavior changes that could affect your store, and how to update without breaking checkout. Version 11.3 is planned for the week of November 9, but it’s still in beta, so keep it off your live store for now.
Attackers don’t pick stores at random. They look for old versions, because they already know what’s broken in them. That’s why a security update isn’t something you leave for “when there’s time.”
This one is small. But rush it on a Friday afternoon and you could spend the weekend with a checkout that doesn’t take orders. The order you update things in matters as much as updating at all.
It’s a maintenance release, a dot release. Nothing new gets added. It fixes and hardens what’s already there. WooCommerce published it on November 4, 2026, and its release notes describe it as a version with several security updates.
One thing worth being clear about: the release notes don’t list vulnerabilities with CVE numbers. So we won’t tell you “this fixes CVE such-and-such,” because the official source doesn’t say that. What the notes do spell out is which parts of the store were hardened.
11.2.2 also ships a database update. After you install it, WooCommerce will ask you to run it. Don’t skip that step. It’s part of the fix, and one of the changes uses it to clean up affected data in your store.
Stricter checkout. WooCommerce hardened the Store API checkout, which is what the checkout blocks use. If an order can’t be saved, checkout now stops before payment. Before, in some cases, it kept going with a partially saved order. Each checkout request also starts with its own order and payment data now, with nothing carried over from a previous request. In practice: less risk of charging a customer for an order that wasn’t recorded properly.
REST API authentication. Plenty of outside tools (inventory, accounting, shipping) read and write your store’s data using REST API keys. That authentication is now more secure, and so is the decoding of payment profile data.
Taxes, attributes, and CSV imports. Tax calculation for local pickup was hardened. So was the way a product’s default attributes update when you rename a term in a global attribute, plus column-mapping validation in the CSV product importer. The cart now ignores attributes the product doesn’t use.
Admin. Two wc-admin endpoints now require a logged-in admin browser session on top of the permission check that was already there. More on why that might matter to you below.
PayPal Standard. When a customer changed their shipping address in PayPal Standard, shipping and taxes didn’t always recalculate. That’s fixed. If you take PayPal Standard, this prevents charges with the wrong total.
Your customers won’t notice any of this. It’s all under the hood, the kind of work nobody sees until the day it’s missing.
1. Checkout now stops if the order can’t be saved. If one of your extensions runs code when an order is saved, and that code throws an error during Store API checkout, the customer will get a 500 error. Before, checkout carried on with an incomplete order. The new behavior is safer, but a buggy extension can now block sales. That’s why testing checkout after you update isn’t optional.
2. Two admin endpoints now require a browser session. Requests that come in with REST API keys, WP-CLI, or application passwords get a 403 error on those two endpoints. The regular wc-admin dashboard works the same as always. If you use an outside tool that connects one of those ways, ask your developer whether it touches those endpoints. Better to find out before than after.
Don’t delete anything. Write down what’s broken and copy the exact error message. That alone saves hours.
Then, on staging (not your live store), turn off suspect extensions one at a time, starting with checkout, payment, and order-related ones. When the problem goes away, you’ve found the culprit. Look for an update to that extension or talk to your developer.
If the problem is blocking sales, restore your full backup, confirm the store is taking orders again, and investigate calmly on staging. Just keep it temporary. This is a security update, and staying on the old version carries its own risk. WordPress and server error logs usually point to the problem in a single line. If you can’t read them, save them for your developer.
The first beta came out on October 26, 2026, and the final release is planned for the week of November 9. Planned, not promised: the date can slip if testing turns up problems. It’s a big release, with 1,310 commits and 117 contributors as of the beta, according to the official notes.
Here’s what’s most likely to matter to a store owner:
When the final version ships, run the same process again: backup, staging, update, test order.
Yes. WooCommerce released it on November 4, 2026 as a security release and recommends updating as soon as possible. It has no new features.
WooCommerce didn’t publish CVE numbers for this release. The official notes list hardening in Store API checkout, REST API authentication, two wc-admin endpoints, local pickup tax calculation, the CSV importer, and PayPal Standard.
Yes. It’s part of the fix. WooCommerce will prompt you after you install 11.2.2; run it and let it finish.
Most likely an extension is failing when the order is saved. Since 11.2.2, checkout stops in that case instead of continuing with an incomplete order. Turn off extensions one at a time on staging until you find it.
The final release is planned for the week of November 9, 2026. Until then it’s a beta and shouldn’t be installed on a live store.
Updating a store shouldn’t be a gamble. When we update WooCommerce for our clients, we follow this exact process: full backup, update on staging, an end-to-end test order, and monitoring afterward. If something breaks, we catch it on staging, not your customers. We also review your extensions and integrations and get releases like 11.3 ready ahead of time.
Want us to review your store and update it to WooCommerce 11.2.2? Contact us, email [email protected], or call (786) 757-4345.
Sources accessed November 6, 2026.
Black Friday is days away. Here are the 7 checks we run on every WooCommerce store before Friday, plus what you shouldn't touch this week.
Read more →
WooCommerce 11.3.0 and a Stripe Gateway security fix shipped on November 11. Here's what's new, what the Stripe update closes, and an 8-step checklist before Black Friday.
Read more →AI assistant — answers may be inaccurate.