The PHP security alert: what every business should check on its website this week

On 21 October PHP shipped emergency fixes for two critical flaws, and for most businesses the website security check that matters now comes down to three questions for whoever looks after the site.

Technician kneeling at an open server rack with a laptop, the kind of website security check a PHP alert calls for

On 21 October the PHP project released versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two flaws that can let a stranger run their own code on a web server without logging in (PHP security advisory, 21 October 2026). The next day a UK minister told the House of Lords that 32 government services were unavailable and four more partly unavailable, mostly as a precaution (BBC). Eleven days on, the useful question for a business isn't whether the sky is falling. It's whether anyone has actually installed the fix on the server your website lives on, and how you'd know.

What happened, in plain words?

PHP is the programming language behind a big share of the web. W3Techs finds it on 69.1% of the websites whose server-side language it can identify (W3Techs, 1 November 2026). That's a lot of servers. WordPress runs on it, and so do plenty of shops, booking systems and custom-built sites.

On 20 October the PHP security team warned that an emergency release was coming the next day, with two critical fixes rated 9.2 out of 10. The advisory that followed (CVE-2026-109618 and CVE-2026-109619) says every PHP installation that serves web requests is at risk, whatever way it's set up, and that the risk is highest with Apache's mod_php. Researchers have since nicknamed the pair PHP2Shell.

The UK's National Cyber Security Centre published an alert the same day. Its advice to organisations is to find every system running PHP, update it, and if that can't happen quickly, apply the temporary settings PHP published or consider taking the system offline until it's fixed (NCSC). On 26 October the US agency CISA added the flaws to its catalogue of vulnerabilities known to be exploited (CISA). That means attacks have been seen, not just predicted.

So how bad has it been? Quieter than the first two days suggested. The confirmed break-ins so far are few, and the ones that stood out were firewall devices, not websites (The Register, 29 October 2026). SecurityWeek reported on 30 October that a company protecting WordPress sites said that as of 28 October it didn't know of a single WordPress site compromised this way, even though it had logged more than 77,000 attack attempts from over 2,000 addresses. That's good news. It isn't a reason to wait, because people are still working on the attack tools, and PHP's own advisory says updating is the only complete fix.

Does your site run on PHP? How to find out

If your site is built on WordPress, Drupal or Joomla, yes, it does. On WordPress you can see the version yourself in about a minute: go to Tools, then Site Health, open the Info tab and look under Server for "PHP version" (WordPress.org). Write the number down. You'll need it for the first question below.

Other setups are less obvious. A site on a hosted platform you pay for monthly runs on that platform's servers, so the question goes to them, and you'll find most have already posted an answer. A custom web app could be PHP or something else entirely, and only the people who built it can tell you for sure. A site made of plain pages with no admin area may not run PHP at all.

Don't forget the boxes in your office either. The NCSC points out that PHP is built into other products too, and asks organisations to watch for updates from the makers of those devices. Remember that the confirmed break-ins were on firewalls. If your firewall, router or network storage has a web login page, ask whoever handles your IT whether its maker has put out an update this month.

The three questions to ask whoever runs your site

Send these by email, so the answers come back in writing:

  1. Which PHP version does the site run on, and was it updated after 21 October? The answer you want is a number: 8.5.12, 8.4.27, 8.3.36, 8.2.35 or later. "It's fine" isn't a version.
  2. When were the CMS (WordPress or whatever the site uses), the theme and every plugin last updated?
  3. When did someone last restore a backup of the site, and where did they restore it to?

If you're not sure who would even answer those, that's the first thing to fix. Somebody holds the hosting login, and it should be in the company's name. I've written about who owns the code and the logins if that part of your contract is fuzzy.

What "updated" should mean: PHP, CMS, plugins

PHP, the CMS and the plugins are three separate layers that don't update together: PHP lives on the server, and on most hosting it's the host who installs a new build, not your web designer, while WordPress handles its own minor updates without anyone asking. Plugins and themes wait for a person unless someone has switched on automatic updates for them. So "everything's updated" can honestly mean a current WordPress with fresh plugins sitting on PHP from September. This month, that's exactly the gap that matters.

Version numbers can mislead you a little, too. PHP 8.1 and older don't get official releases any more, but some Linux distributions patch old versions themselves, and this time the PHP team even published minimal patches for 7.4, 8.0 and 8.1. So a site on 8.1 isn't automatically exposed, and a site on 8.3 isn't automatically safe if its build is older than 21 October. Here's the part I can't tell you from the outside: whether your particular server's build carries that patch. That lives in your host's update log, and only the host can answer it. If they can't name the update and the date it went in, I'd treat the site as unpatched.

Then there's the calendar. PHP 8.2 gets security fixes until 31 December 2026, and after that, nothing (PHP supported versions). WordPress's own statistics, which I read on 1 November, show 33% of WordPress sites on 8.1 or older and another 22.9% on 8.2 (WordPress.org PHP stats). Add those up and more than half of WordPress sites will be on a PHP version with no official fixes from New Year, unless they move. If your answer to question one is 8.2, this week's update buys you two months. WordPress itself recommends PHP 8.3 or newer, so ask about the move while you've got their attention.

One small extra for your tech person. On 23 October PHP published a follow-up note suggesting session.upload_progress.enabled be set to 0 until its next regular release, because of a third, much less likely issue. It's a single line in the settings. Ask whether it's been done.

Backups you've actually tested

A backup nobody has ever restored is a hope, not a backup. If someone did get in, a copy from before the break-in is how you get your site back. With this flaw, "before" may mean before 21 October, since anything planted then would be sitting in every backup made since. The NCSC asks organisations that couldn't update straight away to check for signs of compromise, and that check is a lot easier with a clean copy to compare against.

What I'd want to hear: at least one copy from before 21 October stored somewhere other than the server itself, and a date when someone last restored a backup to a test address and clicked through it. Pages, forms, checkout if you sell online. If the answer is "we've never done that", book it. It takes an afternoon, and it's the only way to find out a backup is broken on a calm day instead of a bad one.

If it can't be updated today

Sometimes an update has to wait. An old theme that breaks on newer PHP, a custom plugin nobody has tested, a host that schedules upgrades. PHP published temporary settings that reduce the exposure, and it says plainly that they don't make an installation safe. The NCSC's advice for systems that can't be updated or protected that way is to consider taking them offline until they can.

That's a business decision, and it should be yours, not your developer's. Weigh what a day or two offline costs you against the cost of a break-in. Whichever way you go, ask for three things in writing: which temporary measures are in place, the date the real update is booked for, and whether anyone has checked the server for signs that someone already got in. A date, not "soon".

What an ongoing maintenance plan covers

A month like this is what a maintenance plan is for. Security fixes for PHP, the CMS and the plugins go in when they come out, not at the next monthly slot. Backups are kept away from the site and restored now and then to prove they work. And someone reads alerts like the NCSC's on the day they're published, then tells you in plain words whether your site is affected. What that should cost, and how to compare quotes, is in my piece on website maintenance and what you pay for.

We do this for sites we built and for sites someone else built, WordPress included, on our servers or on the hosting you already pay for. We also do one-off security audits and web design when a site is past saving. If you'd like a second pair of eyes on the three answers you get back, send them over or email contact@magnuszgr.com.

If all three come back as a version number, a date and another date, you're done with this alert. If any of them comes back as "not sure", that's an answer too. Built an app with an AI maker? Run the logged-out test too.

Read next