Developer reviews security scan results on a monitor, illustrating WordPress news about WooCommerce security work. Developer reviews security scan results on a monitor, illustrating WordPress news about WooCommerce security work.

WordPress news: WooCommerce details its security changes

A November 6 WooCommerce post explains how AI-assisted scans, human review and a new patch policy are changing the project’s security work. Here are the practical checks for store owners and developers.

WooCommerce’s November 6 security update describes a shift from reacting to vulnerability reports to finding more issues through automated scans. This WordPress news matters to store owners and developers because it also sets out how security fixes will ship, when some extension updates can install automatically, and which software checks are worth making now.

WooCommerce says it has expanded AI-assisted security reviews since late May, while keeping people responsible for validating issues and approving fixes. For site teams, the practical takeaway is to keep every store and extension current, check PHP support, and understand which connected Marketplace stores can receive required extension security updates.

WordPress news: WooCommerce expands proactive security scans

In a November 6 post by Darren Ethier, WooCommerce describes a security effort that now includes scans of its code before outside researchers report vulnerabilities. The post links the work to a sharp rise in security reports and says AI tools have made it easier for researchers, as well as WooCommerce’s own teams, to find potential flaws.

WooCommerce says reports about its products through Automattic’s HackerOne program increased roughly nine times over the past year. It also says about three quarters of valid issues tracked in WooCommerce core since July were rated Medium or Low severity. The post says those issues still need attention, but may require specific conditions or have a more limited impact.

The company’s account of its scanning work includes several stages:

  • In July, an AI-assisted review of a year of WooCommerce releases found every high-severity issue the team already knew about, according to the post.
  • In August, scans of the WooCommerce monorepo and maintained extensions flagged roughly 700 potential issues. Teams reviewed the findings and fixed those they considered valid.
  • Since August, automated scans have run on merges to WooCommerce core’s trunk and release branches. The post says 34 security-related issues surfaced, 18 of which were valid.
  • In October, WooCommerce joined Anthropic’s OSS Scanner program with an initial group of extensions. It reported roughly 200 findings across enrolled projects, with about 90% of findings in the platform software deemed valid after triage.

Those figures describe findings and validation, not a count of confirmed attacks. WooCommerce says its own scans and the scanner programs it joined have surfaced more than twice as many valid core issues as external reports. That makes the distinction between a scanner alert and a verified vulnerability important: the post says teams still check findings, test fixes and review possible side effects.

People still review findings and approve fixes

WooCommerce says incoming reports across Automattic now receive an AI first-pass assessment through an internal tool called SentrySift. The stated purpose is to help people spend less time sorting reports and more time confirming severity and working on fixes. The post is explicit that people make the final decisions: they verify issues, review fixes and approve what ships.

That division of work is the useful detail for developers following the announcement. Automated scanning can raise potential problems, but the reported totals do not mean every alert is a security flaw. WooCommerce says its reviews remain part of the process, and it reports a roughly 77% valid rate across findings in its AI-powered regression review.

Security fixes get a separate release path

WooCommerce says security fixes will generally ship in dedicated patch releases rather than being bundled with regular feature updates. Its stated default is for Critical and High severity fixes to go into the next patch release on the current version. Medium and Low severity fixes are scheduled for the patch release after the next minor version.

The company says the policy is intended to make security updates smaller and easier to apply separately from new features. WooCommerce 11.2.2 was the first release under this approach, and the post says 11.3.1 will follow WooCommerce 11.3.0 with another set of fixes. WooCommerce describes this as a default, not an unbreakable rule: it may include a fix in a regular release when the testing and urgency justify it.

The post also says security work is taking priority over some planned product work, delaying features across WooCommerce products. That is a trade-off the team says it is making while it works to handle the increased security workload as routine work rather than an all-hands response.

Which extension updates can install automatically?

Starting with WooCommerce 11.2, WooCommerce.com can mark an extension’s security release as required. The post says eligible stores connected to WooCommerce.com with an active subscription install that update on their next update check, usually within a day, even if automatic updates are turned off.

This applies to extensions available through the WooCommerce Marketplace, not to every extension or to every WooCommerce update. The post also notes that stores configured in code to block automatic updates can still block them. Store owners should check the installed version after a security release, even when automatic updates are enabled.

Check PHP and every site you manage

WooCommerce’s post treats PHP as part of the store’s security picture. It says WooCommerce 11.3 adds an admin notice for stores running PHP 7.4 or 8.0, that WooCommerce 11.5 is the last release supporting those versions, and that WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer. The post recommends PHP 8.3 or newer.

For store owners and agencies, WooCommerce’s checklist is straightforward: update WordPress, WooCommerce and extensions; inspect the installed versions after security releases; check the PHP version in Tools > Site Health > Info > Server; and confirm with the host that PHP security updates have been applied. It also advises checking each managed site, including public staging and development sites, rather than treating one updated installation as proof that the rest are current.

FAQ

Did WooCommerce say AI approves security fixes?

No. WooCommerce says AI tools help assess incoming reports and scan code, but people verify issues, review fixes and approve releases. A scanner finding is not automatically a confirmed vulnerability.

Do required WooCommerce extension updates apply to every store?

No. The post describes required security updates for extensions available through the WooCommerce Marketplace on stores connected to WooCommerce.com with an active subscription. A store configured to block automatic updates in code can still block them.

What should WooCommerce store owners check first?

Check that WooCommerce, WordPress and extensions are current, then confirm the PHP version and ask the host about PHP security updates. If you manage several stores, check each one, including staging sites.

Start by checking the WooCommerce version and PHP version on every store you manage, then confirm that any available security fixes are installed.

Leave a Reply

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