WooCommerce 11.3.1: Release Notes

Dot Release

WooCommerce 11.3.1 is available now

This security-focused patch release brings fixes across checkout, customer accounts, store permissions, and data handling. Review the changes below and update stores promptly.

Updates

  • 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
  • Released: Nov 19, 2026
  • Security update: Yes
  • Database update: Yes

What’s in this release

Earlier this month, we wrote about what Woo has done about security since June, including the proactive reviews behind recent WooCommerce security updates and why fixes now ship in dedicated patch releases. WooCommerce 11.3.1 continues that work with a broad set of security improvements.

This is a high-level overview of the changes in this release, but you can see the full changelog for individual fixes.

Checkout and order integrity: Address and selling-location checks are stronger across classic and block checkout. The release also improves shipping and tax calculations, payment checks for existing orders, held-stock counts, and handling of concurrent Store API order requests.

Coupon rules: WooCommerce more consistently enforces coupon usage and per-customer limits, allowed-email restrictions, and the store-wide coupon setting. Cart totals are recalculated when coupons are removed through the Store API.

Customer accounts and order privacy: Email verification and account credential handling are stronger. Order links, tracking pages, and account flows reveal less customer information to people who should not have access to it.

Permissions and connections: Store API and order-related REST operations have tighter access checks. The release also strengthens selected admin settings, product-management actions, and connections to Woo services.

Product and data handling: Unpublished product information is better protected, and product attributes and CSV imports are handled more safely. Analytics exports and error logs also better limit potentially sensitive values.

Notes for developers

Template changes: The My Account email-confirmation flow adds a myaccount/form-confirm-email.php template for themes.

Legacy REST API endpoint changes: The legacy wc-admin options REST endpoint now requires the manage_woocommerce capability, which may affect integrations using custom order-only roles.

Store API requests with cross-origin credentials now require an allowed origin: WooCommerce 11.3.1 restricts credentialed cross-origin Store API requests to origins explicitly allowed by WordPress. Headless storefronts that send login cookies to the Store API from another origin must allowlist their storefront origin. Cart-token requests that omit credentials remain supported without this change.

Check a headless Store API integration

Your integration may be affected if all of these apply:

  • Calls the Store API from a different origin than the WordPress site.
  • Includes browser credentials, such as through fetch() with credentials: 'include'.
  • Does not already allowlist that origin in WordPress.

Affected requests may fail with browser CORS errors after updating.

If your integration requires cross-origin login cookies, add its exact, trusted origin through WordPress’s allowed_http_origins filter:

add_filter( 'allowed_http_origins', function ( $origins ) {
	$origins[] = 'https://storefront.example.com';
	return $origins;
} );

If your integration uses cart tokens and does not require login cookies, omit credentials instead. For example, use credentials: 'omit' with fetch(). Test your cart and checkout flows after updating.

WordPress allows its own home and admin origins by default. A headless storefront using a different origin must explicitly allowlist it before sending credentialed Store API requests.


2 responses to “WooCommerce 11.3.1: Release Notes”

  1. For the Template Change, is this something we really need to pay attention to? Or is this a background thing that doesn’t require us to change anything?

    1. Brian Coords Avatar
      Brian Coords

      If your theme overrides template files, you may want to review the new template: https://developer.woocommerce.com/docs/theming/theme-development/fixing-outdated-woocommerce-templates/

Leave a Reply

Your email address will not be published. Required fields are marked *