Community

A Third of WordPress Sites Run PHP That Didn’t Get the php2shell Fix. Maybe.

Featured card: 1 in 3 WordPress sites run old PHP

Last updated 6 November 2026. Based on the PHP project’s 21 October security release, advisories from WordPress.org, Red Hat, Ubuntu and Debian, and WordPress.org’s public PHP statistics, read on 6 November.

Short answer first. On 21 October the PHP project fixed two critical bugs, nicknamed php2shell, that affect PHP itself, not WordPress. If Tools > Site Health > Info > Server shows PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or newer, you’re patched. If it shows anything older, you might still be fine, because many hosts and Linux distros patch old versions quietly. You need to check which case you’re in, and below we show how.

The awkward part is the scale. By WordPress.org’s own numbers, about a third of WordPress sites report a PHP version the PHP project no longer patches at all.

What was fixed

The PHP project gave a day’s warning on 20 October: a critical release was coming the next day at 14:00 UTC, for “two critical vulnerabilities, both rated CVSS v4.0 9.2.” PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 came out on 21 October. The php.net advisory describes them like this:

  • CVE-2026-109618, “RCE via OOM corruption”. When PHP runs out of memory at the wrong moment, it can stop while internal request data is only half set up. Cleanup may then treat that broken data as valid.
  • CVE-2026-109619, “RCE via stale global state”. Some internal state can outlive the memory behind it. A later request handled by the same worker may use that stale state before it gets reset.

RCE means remote code execution, which is about as bad as it gets on a web server. php.net says the risk applies to “all PHP installations serving web requests” and is highest for mod_php. It also says: “There are no complete mitigations, updating is the only safe choice.”

Now the calmer view. Red Hat’s bulletin rates the pair “Important” rather than critical and says “Reliable exploitation requires precise heap manipulation and timing.” On RHEL 8 and later, PHP-FPM workers exit on early initialization failures, which Red Hat says makes RCE difficult in practice. mod_php setups are at higher risk. Nobody we’ve read claims these are being exploited, and they’re not on CISA’s exploited list as of 6 November.

So: serious, worth fixing this week, not a reason to panic.

WordPress.org posted about it too on 21 October. No WordPress update is needed, since this isn’t a WordPress bug. But the post makes one point plainly: “Versions of PHP prior to 8.2 no longer receive security updates from the PHP project.” For people who run their own server on older PHP, it quotes the UK NCSC’s advice to “consider taking your server offline while you prepare to update.”

A few smaller follow-ups landed after. On 23 October php.net published an informational advisory, CVE-2026-115560, about session upload progress (“an unlikely RCE vector”) and suggested session.upload_progress.enabled=0 until the next release. On 26 October the Windows builds were updated for a Brotli bug (CVE-2026-111497) that’s reachable through cURL auto-decompression, which is off by default.

Which PHP versions WordPress sites actually run

We pulled WordPress.org’s PHP stats on 6 November 2026. This is the share of WordPress sites reporting each version:

PHP version Share of WordPress sites Gets fixes from the PHP project?
8.5 (plus 0.02% on the 8.6 release candidate) 6.28% Yes
8.4 10.56% Yes
8.3 27.75% Yes
8.2 22.73% Yes, until 31 December 2026
8.1 9.26% No
8.0 3.39% No
7.4 14.65% No
7.0 to 7.3 3.41% No
5.x (5.2 to 5.6) 1.94% No

Add up the “No” rows and you get 32.65%. About one WordPress site in three reports a PHP version that didn’t get the php2shell fix from the PHP project. Upstream-supported versions, 8.2 and newer, cover 67.35%.

There’s a slow drift the right way. In our own earlier snapshots of the same API, PHP 7.4 was 16.3% on 14 October and is 14.65% now. Sites below 8.1 were 25.8% on 18 October and are 23.4% now. These shares wobble from day to day, so we’d only call that “a little lower”, not a trend.

WordPress itself doesn’t push hard here. Core still installs on PHP 7.4. WooCommerce is moving faster, with a PHP 8.1 minimum planned for February 2027.

Why that third isn’t the whole story

Here’s the “maybe” in the title. The PHP project only patched 8.2 and newer. But Linux distributions and hosting platforms take fixes and backport them into the old version numbers they ship. The version stays “7.4”, the code inside it gets patched.

Ubuntu shipped php2shell fixes all the way back to 14.04:

Ubuntu release PHP package Fixed version Who gets it
26.04 php8.5 8.5.4-0ubuntu1.5 Standard support
24.04 php8.3 8.3.6-0ubuntu0.24.04.13 Standard support
22.04 php8.1 8.1.2-1ubuntu2.28 Standard support
20.04 php7.4 7.4.3-4ubuntu2.29+esm5 Ubuntu Pro (ESM)
18.04 php7.2 7.2.24-0ubuntu0.18.04.17+esm14 Ubuntu Pro (ESM)
16.04 php7.0 7.0.33-0ubuntu0.16.04.16+esm22 ESM Legacy
14.04 php5 5.5.9+dfsg-1ubuntu4.29+esm18 ESM Legacy

Debian is similar but with a gap. Trixie’s php8.4 is fixed in 8.4.27-1~deb13u1, and bookworm got a fix through an LTS advisory (the Debian security tracker has the details). Bullseye, Debian 11, left LTS on 31 August 2026, so it reportedly gets no free fix.

CloudLinux, which a lot of shared hosts run, shipped fixed alt-php and ea-php builds, reportedly all the way back to ea-php52.

Put that together and a site showing “PHP 7.4” could be in either camp. Patched, if the host runs CloudLinux or pays for Ubuntu Pro and has installed the update. Not patched, if it’s a self-built PHP or an end-of-life distro nobody’s paying to support. The version number alone can’t tell you.

How to read your Site Health PHP version

Go to Tools > Site Health > Info and open Server. Look at “PHP version”. On Ubuntu and Debian builds, the version includes the distro’s suffix, like 8.1.2-1ubuntu2.28, and Site Health shows it in full. A plain upstream build shows just the number, like 8.4.26. That difference is the whole trick.

Case 1: a current upstream version

You see 8.2.35, 8.3.36, 8.4.27, 8.5.12 or something newer. You’re patched. Done.

Case 2: an older number with a distro suffix

You see something like 8.1.2-1ubuntu2.28 or 7.4.3-4ubuntu2.29+esm5. Compare it with the fixed version for your distro in the table above, or in your distro’s tracker. Same or higher means the backport is in. Lower means it isn’t yet.

Case 3: a bare old number

You see something like 7.4.33 with no suffix. That could be a vendor build that’s been patched, or a build nobody has touched in years. Site Health can’t tell you which. Ask your host, in writing.

What to send your host

Keep it short. Something like this does the job:

Hi, my site shows PHP [version] in Site Health. Is the PHP build serving my site patched for CVE-2026-109618 and CVE-2026-109619 (php2shell)? Which package version is it? Thanks.

A good host answers that in a line. If the answer is vague, or they don’t know what you’re asking about, that tells you something too.

If you run your own server

  1. Run apt update, then upgrade your PHP packages.
  2. Restart PHP-FPM or Apache. The fix only applies once the running PHP processes are replaced. Ubuntu says unattended-upgrades will install it within 24 hours, but it still won’t take effect until the restart.
  3. Check Site Health again and confirm the version string matches the fixed one.

If you can’t patch straight away, Red Hat lists some stopgaps: set session.upload_progress.enabled=0, and cap post_max_size at 8M or 32M with upload_max_filesize below it. Red Hat is clear these aren’t a substitute for patching. If you’re on an end-of-life distro with no fix coming, the honest answer is a move to a supported PHP.

The next date: 31 December 2026

The PHP 8.2.35 release notes say it plainly: “PHP 8.2 reaches end of life on 31 December 2026 and will receive no further security fixes after that date.”

That’s 22.73% of WordPress sites. Add them to the 32.65% already below 8.2 and roughly 55% of WordPress sites would be on PHP with no upstream support next year, if nobody moves. Backports will cover some of them, same as now. But that’s a lot of sites leaning on their host’s goodwill.

If you’re on 8.2, plan the jump to 8.3 or 8.4 before the end of the year. Make a staging copy, switch its PHP, click through the things that matter (forms, checkout, logins, anything custom), then switch live. Updated plugins and themes handle most of it.

This has been a busy year for patching in general. We covered the run of WordPress security releases in 2026 separately, and the same day as this post, the WordPress core upgrader flaw, CVE-2026-119977.

Frequently asked questions

Do I need to update WordPress for php2shell?

No. php2shell is a bug in PHP, not in WordPress, and WordPress.org says no WordPress update is needed. The fix comes from updating PHP on your server, or from your host doing it for you.

My site shows PHP 7.4. Is it vulnerable?

Maybe. The PHP project no longer patches 7.4, but some distros and hosts backport fixes into it, including Ubuntu Pro and CloudLinux builds. If Site Health shows a distro suffix, compare it with your distro’s fixed version. If it shows a bare number, ask your host whether their build has the fix for CVE-2026-109618 and CVE-2026-109619.

When does PHP 8.2 stop getting security fixes?

On 31 December 2026. About 22.73% of WordPress sites run PHP 8.2, so plan a move to 8.3 or 8.4 before then and test it on a staging copy first.