Skip to content
ShopifyWixBigCommerceWordPress

PHP Security Update for WooCommerce Stores: What to Do

When PHP ships a security update, WooCommerce stores need a patched PHP from their host. Shopify, Wix and BigCommerce stores ask their app vendors instead.

BarcodeMan Team About 8 min read

When PHP ships a security release, what you do depends on where your store runs. For a PHP security update on WooCommerce, the fix is a new PHP build on your web server, and you or your hosting company installs it. Updating WooCommerce or a plugin does not change PHP. On Shopify, Wix, and BigCommerce, your store itself has no PHP to update, and your part is to ask the developers of your apps whether their servers are patched. If you also run a WordPress site, the WooCommerce sections apply to it.

This guide shows how to check your PHP version, why an old-looking version number can still be patched, what to do on PHP 7.4, 8.0, or 8.1, and what to ask your host and your app vendors. The October 2026 release is the worked example.

The latest PHP security release (21 October 2026)

On 21 October 2026, the PHP project released PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. They fix two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that can allow unauthenticated remote code execution. PHP scores both 9.2, critical, on CVSS v4.0. The php.net security advisory says “All PHP users are strongly encouraged to update immediately.”

The advisory puts “all PHP installations serving web requests” at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. It rates the risk highest for mod_php. A WooCommerce store is a PHP installation that serves web requests, so it is in scope. The per-branch release notes add that “There are no complete mitigations, updating is the only safe choice.”

PHP 8.1 and older got no official release for these two bugs. See If you’re on PHP 7.4, 8.0, or 8.1.

On 23 October 2026, php.net posted a follow-up about a separate issue it will publish as CVE-2026-115560. php.net says the issue “can only occur under an unusual combination of configuration and application code” and that a full advisory comes with the next release. If your host asks about it, point them to php.net’s note.

Who has to act depends on your platform

PlatformWho runs the serverWhat you do
WooCommerce on WordPressYour hosting company, or you if you run your own serverCheck your PHP version and get the fixed build installed
ShopifyShopifyAsk your app vendors whether their servers are patched
WixWixAsk your app vendors whether their servers are patched
BigCommerceBigCommerceAsk your app vendors whether their servers are patched

On Shopify, Wix, or BigCommerce, ask your app vendors

These platforms run and patch the servers behind your store. Your store admin has no PHP setting to check. The apps you install are a separate case. Each app’s backend runs on servers its developer runs or rents, in whatever language the developer chose, and that developer is responsible for patching them.

To get an answer from an app vendor, send them this message:

Hi, PHP released security fixes on [date] for [CVE numbers].
1. Does your app's backend run PHP anywhere?
2. If it does, which PHP version, and when did you install the fixed build?
3. Do any services you rely on for my store's data run PHP? Are they patched?
4. Where do you publish security notices?

For the October 2026 release, the date is 21 October 2026 and the CVE numbers are CVE-2026-109618 and CVE-2026-109619. “We don’t run PHP” is a complete answer to the first question. For BarcodeMan’s answer on each platform, see Security and the software BarcodeMan runs.

On WooCommerce, your host’s PHP runs your store

WordPress, WooCommerce, and every plugin are written in PHP. PHP itself is a program installed on your web server, and that one program runs all of them. A PHP security bug is a bug in that program. The PHP 8 ChangeLog files the October 2026 fix under Core, the PHP engine, and not under WordPress, WooCommerce, or any extension.

This is why updating WordPress, WooCommerce, or a plugin does not patch PHP. The GitHub advisory for CVE-2026-109618 says that updating to a PHP release with the patch “is the only complete mitigation.”

BarcodeMan for WooCommerce works the same way. Our plugin runs inside your WordPress site on your host’s PHP, like every other plugin, and updating it leaves PHP unchanged.

If you rent hosting, your host installs the PHP builds. If you run your own server, install the PHP security update from your Linux distribution or rebuild PHP from the fixed release.

How to check your PHP version in WooCommerce

You can read the version from WordPress or from WooCommerce.

To check it in WordPress:

  1. Go to Tools > Site Health.
  2. Open the Info tab.
  3. Expand the Server section. It lists the PHP version.

To check it in WooCommerce:

  1. Go to WooCommerce > Status.
  2. Find the PHP version row in the Server Environment section.

WordPress documents the first path on its Update PHP page, and WooCommerce documents the second in its System Status Report guide. Neither screen tells you whether your host added a security fix to that build. The next section explains why that matters.

An older version number can still be patched

Some Linux distributions fix a security bug by copying the patch into the PHP version they already ship. The version number stays the same. This is called a backport.

The October 2026 fix shows both approaches:

  • Ubuntu 24.04 ships PHP 8.3 as package 8.3.6-0ubuntu0.24.04.13. That package has the fix, although the upstream number 8.3.6 is lower than 8.3.36.
  • Debian 12 moved to the new upstream release and ships PHP 8.2 as package 8.2.35-1~deb12u1.

So if WooCommerce > Status reads 8.3.6, your site is not necessarily exposed. If the number is at or above the fixed release for your branch, such as 8.3.36 on PHP 8.3 for the October 2026 release, the build includes the fix. If it is below, only your host can tell you whether the build is patched.

If you’re on PHP 7.4, 8.0, or 8.1

The php.net advisory says “PHP 8.1 and older no longer receive updates from the PHP project.” For the October 2026 bugs, the PHP security team published minimal source backports for 7.4, 8.0, and 8.1 “to help people building from source or without access to an LTS vendor.” They are source code, not an update you install from wp-admin.

The same advisory says “Some distributions and LTS vendors provide backported fixes.” For example, Ubuntu 22.04 shipped a fixed PHP 8.1 package, and Ubuntu 20.04 shipped a fixed PHP 7.4 package only through Ubuntu Pro.

WordPress and WooCommerce both still run on PHP 7.4. The WordPress requirements page warns that these versions “have reached their official End Of Life and may expose your site to security vulnerabilities.”

If your site runs PHP 7.4, 8.0, or 8.1, do these steps:

  1. Ask your host whether your current build has a backported fix. The questions are in What to ask your hosting company.
  2. Plan a move to PHP 8.3 or newer. WordPress recommends PHP 8.3 or greater, and WooCommerce’s server requirements recommend “PHP version 8.3 or greater (tested up to PHP 8.4).”
  3. Back up your site before you switch.
  4. After the switch, check the version again with the steps in How to check your PHP version in WooCommerce.

PHP 8.2 gets security fixes only until 31 December 2026, so a move to 8.2 now means a second move soon.

WooCommerce 11.6 will require PHP 8.1

WooCommerce announced on 29 September 2026 that WooCommerce 11.6, planned for February 2027, requires PHP 8.1 or newer. It also says that “WooCommerce 11.3 will add a dismissible admin notice for stores running PHP 7.4 or 8.0.”

PHP 8.1 meets that minimum but no longer gets official PHP releases. Plan your PHP move past 8.1 so you upgrade once.

PHP end-of-life dates for WooCommerce stores

After a PHP branch reaches the end of its security support, the PHP project releases no more fixes for it. Dates come from php.net’s supported versions and end-of-life pages.

PHP branchEnd of security support
8.531 December 2029
8.431 December 2028
8.331 December 2027
8.231 December 2026
8.131 December 2025
8.026 November 2023
7.428 November 2022

What to ask your hosting company

Send this message to your host’s support team, and fill in the date and CVE numbers from the php.net advisory:

Hi, PHP released security fixes on [date] for [CVE numbers].
1. Which PHP version and build does my site run?
2. Does that build include these fixes? If you backport fixes,
which package version has them?
3. If my site runs PHP 8.1 or older, do you supply backported
security fixes for it, and until when?
4. Can I move my site to PHP 8.3 or newer, and how?

For the October 2026 release, the date is 21 October 2026 and the CVE numbers are CVE-2026-109618 and CVE-2026-109619.

Frequently asked questions

Does updating WooCommerce update PHP?

No. WooCommerce runs on PHP and does not install it. Your host, or you on your own server, installs PHP. A PHP security fix reaches your store only when that PHP build is updated.

Is Shopify affected by a PHP vulnerability?

Shopify runs and patches its own servers, and you have no PHP to update. The apps in your store run on their developers’ servers, so send each developer the questions in On Shopify, Wix, or BigCommerce, ask your app vendors. Wix and BigCommerce stores work the same way.

Can a security plugin protect my store instead of a PHP update?

No. A security plugin is not a substitute for the PHP update. The GitHub advisory for CVE-2026-109618 says the validated attack on mod_php happens “entirely before any application-specific code begins execution,” and php.net says updating “is the only safe choice.”

Where does PHP announce security releases?

php.net posts them in its news archive. For the October 2026 release, it posted a pre-announcement on 20 October with the release time.