DEV Community

Eric Culus
Eric Culus

Posted on Edited on Originally published at rescuemysites.com

WooCommerce 11.3.1: the security patch that can break headless checkouts

WooCommerce 11.3.1 shipped on 19 November 2026 as a security release. If your storefront calls the Store API from another domain with cookies, expect CORS errors until you allowlist that origin.<br>

On Thursday 19 November 2026 WooCommerce released 11.3.1, a patch release the team labels as a security update, with a database update attached. The release notes describe it as bringing "fixes across checkout, customer accounts, store permissions, and data handling" and ask store owners to update promptly and then test cart and checkout. No CVE ids, severity scores or reports of attacks are attached to it.

For most WooCommerce stores that is the whole story: update, place a test order, done. The reason it is worth a longer look here is that 11.3.1 also tightens how the Store API answers requests from other domains. That is exactly the setup a lot of AI-built shops use, and it is the kind of change that turns a working checkout into a console full of red CORS errors the morning after an automatic update.

Why a patch release, and why now?

WooCommerce explained the context on 6 November in a post titled "We went looking: what Woo has done about security since June". Reports to its HackerOne programme rose roughly ninefold over the past year as AI tools made bugs cheaper to find, and deep scans in August flagged around 700 potential issues to triage. Since then every merge into trunk and the release branches gets an automated security scan, and security fixes go out in dedicated patch releases by default: Critical and High issues in the next patch on the current version, Medium and Low in the patch after the next minor release. The same post named 11.2.2 and 11.3.1 as the releases carrying the fixes from that work.

So 11.3.1 is not a reaction to an attack. It is a batch of hardening that landed on schedule. The public notes stay at summary level ("stronger checkout, order, shipping, tax, and coupon checks", "better protection for customer accounts and order information", "tighter API permissions and safer handling of product and store data"), and the WordPress.org changelog lists the individual fixes as plain "Fix" lines. One of those lines is the one that matters most to anyone with a decoupled front end: "Protect customer account data from untrusted cross-origin cart requests."

Does this reach your app?

It does if your storefront is a separate front end, the typical Lovable, Bolt, v0 or Next.js shop that renders products itself and talks to WooCommerce over the Store API (/wp-json/wc/store/v1/...). The question is how those requests are authenticated.

If the front end runs on a different origin from WordPress (say shop.example.com in front of cms.example.com, or a *.vercel.app preview in front of your live WordPress) and it sends requests with credentials: 'include' so the WordPress login cookie travels along, 11.3.1 now only honours that when the calling origin is one WordPress allows. Anything else is refused, and in the browser that surfaces as a CORS error on cart, checkout or account calls. The release notes say so directly: affected requests "may fail with browser CORS errors after updating."

It does not reach you if your front end and WordPress share an origin, if you only make server-side calls from your own backend, or if your cart works with the Store API's cart token and never sends cookies. WooCommerce notes that cart-token requests without credentials keep working.

There is a common AI-generated pattern worth checking for specifically: a fetch wrapper with credentials: 'include' added "to make the cart persist", copied onto every Store API call. It often works by accident on a same-origin setup and then breaks the first time the front end moves to its own domain or a preview URL. After 11.3.1 it breaks on any origin you have not allowlisted.

What to check and change today

Start by finding out what you are running. In WordPress go to Plugins and read the WooCommerce version, or run wp plugin get woocommerce --field=version if you have WP-CLI. If it already says 11.3.1, the change is live and you should test now. If it is older, update on a staging copy first.

Then go through this list:

  1. Search the front end for Store API calls: grep -rn "wc/store" src app lib. For each one, note whether it sets credentials: 'include'.
  2. If a call needs the logged-in customer (account pages, saved addresses, order history), keep the credentials and allowlist your storefront's origin in WordPress.
  3. If a call only needs the cart, consider switching it to the cart token and credentials: 'omit', which WooCommerce documents as unaffected.
  4. Open the storefront in a private window, add a product, go through checkout to the payment step, then log in and load the account page. Watch the browser console and network tab for CORS failures on /wp-json/wc/store/.
  5. Repeat on your preview domain if you use one, since that is a different origin from production.

The allowlist uses the standard WordPress filter allowed_http_origins, in a small must-use plugin or your theme's functions.php:

add_filter( 'allowed_http_origins', function ( $origins ) {
    $origins[] = 'https://shop.example.com';
    return $origins;
} );
Enter fullscreen mode Exit fullscreen mode

List exact origins, scheme included. Resist the temptation to add a wildcard or to reflect whatever Origin header arrives: that recreates the hole the patch closes, because the point of the change is that a random site should not be able to make a logged-in customer's browser read their account data.

The two smaller changes worth a test

The legacy wc-admin options REST endpoint now requires the manage_woocommerce capability. If you created a custom role for staff who only handle orders, or an integration user with a narrow role, and something in your admin tooling reads store options through that endpoint, it will start returning permission errors. The fix is either to give that role the capability deliberately or to stop depending on the legacy endpoint; do not hand out manage_woocommerce just to make an error go away without knowing what reads it.

Version 11.3.1 also adds a template, myaccount/form-confirm-email.php, for the My Account email-confirmation flow. Themes that override My Account templates should check WooCommerce's template status screen (WooCommerce, Status, Templates) for outdated overrides, and you should walk through the account pages once in a browser. Headless front ends that rebuild My Account themselves will not render this template, so check whether the confirmation flow needs an equivalent screen on your side.

Should you hold the update back?

No. Holding a security release to protect a fragile integration is the wrong trade, and the fix for the integration is a few lines. The sensible order is: copy the site to staging, update there, run the checks above, add the origin filter if you need it, then update production and repeat the test order. If you are on managed WordPress hosting that applies plugin updates for you, assume 11.3.1 is either already live or will be soon, and run the browser test today rather than waiting for a customer to tell you checkout stopped working.

If you find that your store's checkout logic is spread across generated code you no longer fully understand, the logins and sessions guide covers the same cookie and origin questions from the other side.


Originally published on RescueMySites. Sources: WooCommerce 11.3.1 release notes, WooCommerce security post of 6 November, WordPress.org changelog.

Top comments (0)