← All posts

WooCommerce Automatic Security Updates: What Still Needs You

WooCommerce automatic security updates now exist in a narrow form: since WooCommerce 11.2, WooCommerce.com can mark an extension’s security release as required, and connected stores with an active subscription install it on their next update check, usually within a day, even if auto-updates are switched off. That covers some of your extensions. It does not cover WooCommerce core, your PHP version, your theme, plugins bought elsewhere, or the question of whether checkout still works afterwards.

The facts below come from the WooCommerce developer blog post We went looking: what Woo has done about security since June (6 November 2026), the WooPayments security notice (3 November) and the WooCommerce 11.3.0 release notes (11 November), read on 17 November 2026. Policies like this change, so recheck the sources if you are reading later.

What changed in WooCommerce automatic security updates

Two separate things were announced, and they are easy to mix up.

A patch release policy. According to the developer blog, the defaults are now:

  • Critical and High severity fixes ship in the next patch release on the current released version.
  • Medium and Low severity fixes ship in the patch release after the next minor version.

The post calls these defaults, not hard rules, so an important fix can still arrive in a regular release. It names WooCommerce 11.2.2 as the first release under this approach and says 11.3.1 follows 11.3.0. In practice, expect more small dot releases, and treat them as security releases until the release notes say otherwise. My own read is that a store on a monthly update rhythm will now sometimes be a patch behind for weeks.

Required security updates for extensions. WooCommerce.com can mark an extension’s security release as required. Per the post, this applies only to security fixes, only after the extension developer has published the fixed version, and only to extensions sold through the WooCommerce Marketplace on stores connected to WooCommerce.com with an active subscription. A store that blocks automatic updates programmatically can still do so, though the post names no specific setting for that.

What this does not cover

Read the scope carefully, because “automatic” invites the assumption that you are safe.

  • WooCommerce core. The required-update mechanism is described for Marketplace extensions. Core still follows your normal update routine or WordPress auto-update settings.
  • Extensions from other sources. Plugins from WordPress.org, a vendor’s own site or a custom build are outside what the post describes.
  • Disconnected or lapsed stores. The mechanism needs the store connected to WooCommerce.com with an active subscription.
  • Verification. The WooPayments notice still tells store owners to check the installed version “even if automatic updates are enabled” or if a host manages updates, and says a completed update on one site does not confirm the status of another.
  • Regression testing. An automatic install happens without anyone clicking through your checkout afterwards.

That last point is the one I would weight most. A security fix to a payment or shipping extension is exactly the kind of update where a changed hook or a stricter validation can alter checkout behavior. The WooCommerce 11.3.0 notes, for instance, list validation of REST API refund allocations among the developer changes, which is the sort of tightening an integration can trip over. Our guide to updating WooCommerce plugins safely with a staging workflow covers the test pass; the point here is that it now has to also happen after updates you did not trigger.

A weekly check that fits automatic updates

Automation shifts the work from “apply the update” to “confirm the update, then confirm the store”. A reasonable routine:

  1. Look at the installed versions. In wp-admin, open Plugins > Installed Plugins and compare WooCommerce, WooPayments, your payment gateways and any extension named in a recent security notice against the fixed versions in the official announcement. Do this on every environment, including staging and any forgotten development copy.
  2. Check the connection. In your WooCommerce.com account and in the store’s WooCommerce extensions area (menu names vary by version), confirm the store is still connected and the subscriptions for your key extensions are active. A lapsed subscription quietly removes a safety net.
  3. Run a short checkout pass. Place a test order, using the gateway’s test mode where it offers one, then confirm the order status, the customer email and the stock change. Test a shipping and tax case that is specific to your store.
  4. Read the order list. Look for orders stuck on pending payment or on hold after an update window. If you see them, our guide to orders stuck on pending payment or on hold walks through the usual causes.
  5. Keep a rollback path. Before any update window, make sure a recent backup exists that you have actually seen restore, or can restore on staging.

If you rely on a host that manages updates, ask what it updates, when, and whether it tests checkout. Do not assume the answer.

PHP is the part automation will not fix

The same developer blog post carries a timeline that matters more than most plugin notices. It says PHP versions before 8.2 no longer get security updates from the PHP project, and that about 9 percent of the stores WooCommerce tracks run PHP 7.4 or 8.0. WooCommerce 11.3 adds an admin notice for those versions. The post says 11.5 is the last release supporting PHP 7.4 and 8.0, and that 11.6, planned for February 2027, requires PHP 8.1 or newer, with 8.3 or newer recommended.

To see your version, go to Tools > Site Health > Info > Server. If it shows 7.4 or 8.0, a plugin security fix does not help with an unsupported runtime underneath it. We covered the upgrade preparation in PHP 8.2 end of life and the WooCommerce upgrade checklist. Change PHP on staging first, because custom code and older extensions are where version jumps tend to fail.

When this becomes an engineering problem

Most stores can run the weekly check above themselves. It becomes a job for an engineer when:

  • A security update lands and checkout, shipping or a payment flow behaves differently, and the cause is not obvious.
  • You run custom plugins or integrations that call WooCommerce hooks, and you need them reviewed against a new release.
  • You are stuck on an old PHP version because something custom will not run on a newer one.
  • You manage several client stores and need a repeatable version-tracking and testing process.

What to watch next

Watch the WooCommerce developer blog for 11.3.1 and the first fixes that arrive under the new patch policy, and for the WooCommerce 11.6 requirements as February 2027 approaches. WordPress 7.2 is in beta at the time of writing, so a compatibility pass on staging is worth planning for its release. None of these dates are guarantees, so check the official posts before acting.

A final caution: a policy that installs security fixes faster reduces one kind of risk and adds the need to confirm the result. Treat the automatic install as the start of the update, not the end of it.

Want security updates verified and tested before they touch checkout?

The Care Plan covers updates tested on staging first, a full regression pass and a written update each cycle.

See the Care Plan