The latest PHP security update came out on 19 November 2026, and it is one update your WordPress dashboard cannot install for you. PHP is the programming language WordPress and WooCommerce run on. It lives on the server, so your host, or whoever manages your server, has to apply the fix.

Here is our view as web developers. Most business owners know plugins need updating. Far fewer know which PHP version their site runs, or that one of the versions patched last week stops getting security fixes on 31 December 2026. This is a good week to find out.

What do we know about the PHP security update?

  • 18 November 2026. The Register reported that more PHP patches were being released, covering all supported versions and including at least one rated critical. It quoted the advisory as saying the critical issues "require either non-default configuration or uncommon setups".
  • 19 November 2026. BleepingComputer reported that the updates were released that day for all supported branches, as PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, and that they fix 18 flaws. The most severe one it describes is in PHP-FPM, a common way of running PHP on a web server. It is rated 9.2 out of 10 and allows code to be run without a login, but only in certain server setups.
  • The PHP project calls PHP 8.2.36 a security release and encourages all PHP 8.2 users to upgrade to it.
  • Patchstack's analysis counts seven of the 18 as critical. It also makes the point that matters most for site owners: none of these are WordPress bugs. They sit in the layer beneath it, so this is a host-level update and patching WordPress does nothing for it.

What we do not know is just as important. The reports we read do not say whether any of these flaws has been used in an attack. And nobody outside your hosting account can tell you whether your server uses one of the affected setups, or whether the fixed release is installed yet. Those are questions for your host.

Which PHP versions still get security fixes?

Each PHP version is supported for a fixed period, then it stops receiving fixes. The PHP project's supported versions page lists the end dates for security support:

  • PHP 8.6, released on 19 November 2026: until 31 December 2030.
  • PHP 8.5: until 31 December 2029.
  • PHP 8.4: until 31 December 2028.
  • PHP 8.3: until 31 December 2027.
  • PHP 8.2: until 31 December 2026.

Anything older is already out of support. The project's list of unsupported branches shows PHP 8.1 reached end of life on 31 December 2025, with 8.0 and 7.4 ending years earlier. Patchstack notes that 8.1 and earlier received nothing in this release. For WordPress sites, the WordPress requirements page recommends a host that supports PHP 8.3 or greater.

What this means for your website

A website is a stack of layers: the server, PHP, WordPress, then themes and plugins. Most maintenance attention goes to the top layers because that is where the Update buttons are. This release is a reminder to look further down. Here are four checks, in the order we would do them.

1. Which PHP version does your site run?

You can find this in a minute. In WordPress, open Tools, then Site Health, then the Info tab. The Server section shows your PHP version.

  • Write down the full version number, for example 8.3.37, not just 8.3.
  • No WordPress? Look in your hosting control panel under PHP settings, or ask your host.
  • If you run more than one site, check each one. They can differ, even on the same hosting account.

2. Has your host installed the fixed release?

On most shared and managed hosting, the host applies these small PHP releases for you. How quickly they do it varies. On a virtual private server or cloud server, it is the job of whoever manages that server, and it does not happen by itself.

  • Ask your host: "Are we on PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or later?"
  • If the answer is no, ask when the release will be installed.
  • If you or your developer run the server, book the update now and restart PHP afterwards.

3. Is your site on PHP 8.2 or older?

Then you have a deadline or a problem. PHP 8.2 loses security support in about five weeks. PHP 8.1 and older already have no fixes, including for the flaws patched last week.

Moving to a newer PHP version is usually a setting in your hosting panel, but do not flip it on a live site and hope. Older plugins, themes and custom code can fail on a newer version.

  • Copy the site to staging and switch the copy to PHP 8.3 or newer.
  • Test what earns you money: forms, checkout, bookings and login.
  • Update or replace anything that breaks, then switch the live site.

Online stores have an extra reason to move. WooCommerce has said version 11.6, due in February 2027, will require PHP 8.1 or newer, and that it recommends 8.3 or newer. WooCommerce 11.3 also adds an admin notice for stores still on PHP 7.4 or 8.0.

4. Who looks after the layer under your website?

Earlier this month the urgent fix was in WordPress itself, when a WordPress vulnerability was being used in attacks. This time the fix sits underneath. A site is only looked after when someone owns every layer.

  • Find out who is responsible for PHP on your site: the host, your developer or nobody.
  • Put 31 December 2026 in the calendar if you are on PHP 8.2.
  • Keep your hosting login somewhere you can find it, with a second person who has access.

What this means for web development in Australia

For our industry, the PHP version belongs in every handover and every maintenance plan. Many sites are launched on whatever PHP version the host offered that day, and it is never looked at again. We think a build is not finished until the owner knows which PHP version it runs, when that version stops getting fixes, and who will move it. One concrete step for any business: ask your developer or host for those three facts in writing.

How Web Mage can help

If you are not sure what your site runs on, we can find out and tell you plainly.

  • Our website maintenance plans start with a site check that reviews your hosting, plugins, backups and security. Updates are then tested on a staging copy before they go live.
  • When a plugin, theme or custom feature will not run on a newer PHP version, our WordPress developers can update the code or replace it with something supported.

Not sure which PHP version you are on, or who is meant to update it? Contact us with your site address and we will tell you where you stand.