If you run a WordPress website, you may have seen the name PHP2Shell in the news towards the end of October. Government websites in several countries were switched off for a while, and the UK’s National Cyber Security Centre told organisations to act straight away.
It sounds alarming, and it was serious. But for most small business websites, the fix is straightforward once you know who is responsible for which part. This post explains what happened in plain English and what I’d do now if it were my site.
What PHP2Shell is
PHP is the programming language that WordPress is written in. It runs on the web server and builds your pages each time someone visits. WooCommerce, most WordPress plugins and many other website systems depend on it too.
On 21 October 2026 the PHP project published fixes for two serious flaws, tracked as CVE-2026-109618 and CVE-2026-109619 and known together as PHP2Shell. Both could let an attacker run their own code on a web server without logging in. The PHP project rated each one 9.2 out of 10 for severity.
The flaws were in PHP itself, not in WordPress. That matters, because it means a well-kept WordPress site with every plugin up to date could still be exposed if the server underneath it hadn’t been fixed.
How it unfolded
- 20 October: the PHP security team gave advance notice of an urgent release. Details leaked online the same day.
- 21 October: fixed versions came out: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The PHP project said updating was the only complete fix.
- 21 October: the NCSC published guidance for UK organisations. Over the next day or so, public bodies in Finland, the Netherlands, Germany and France took some of their own sites offline as a precaution while they patched.
- In the days after: reports of attack attempts grew. Cloudflare and Amazon both said they had seen attempts to exploit the flaws, some before the fixes were even public.
Which versions are affected
The flaws go back a long way. Reporting put the oldest affected release at PHP 5.4, from 2012, and every version since.
If your site runs PHP 8.2, 8.3, 8.4 or 8.5, there is an official fixed release for it. If it runs PHP 8.1 or older, the PHP project no longer supports it. The security team did publish minimal code fixes for 7.4, 8.0 and 8.1 for people who build PHP themselves, and some hosting control panel and operating system vendors released their own patched builds. But the clear advice from the PHP project is to move to a supported version.
One more date to note: PHP 8.2 reaches the end of its life on 31 December 2026. If your host has just patched you on 8.2, you will need to move up again soon.
The part that surprises people
Clicking “Update” in your WordPress dashboard does not fix PHP. PHP sits on the server, and on most shared or managed hosting only your hosting company can update it.
So there are really three separate jobs here, often done by three different people:
- Your hosting company updates PHP and the server.
- You, or whoever looks after your site, updates WordPress itself.
- You, or whoever looks after your site, updates the theme and every plugin.
A week after PHP2Shell, on 28 October, WordPress released version 7.1.4 with fixes for 22 separate issues in WordPress itself, including one in the update process that could lead to someone running code on the server. That release is unrelated to PHP2Shell, but it landed at the same time and needs installing too. WordPress also released matching fixes for older branches, back as far as 4.7.
What to do now
You don’t need to be technical to work through this. Set aside half an hour.
1. Find out which version of PHP you’re on
Log in to WordPress and go to Tools, then Site Health, then the Info tab. Open the Server section and you’ll see the PHP version listed. Write it down.
If you can’t log in, or the site isn’t on WordPress, ask whoever built it or your hosting company.
2. Ask your host, in writing
Send your hosting company a short email asking:
- Have you installed the PHP security fixes released on 21 October 2026 for CVE-2026-109618 and CVE-2026-109619 on the server my site uses?
- When was it done?
- If my site is on PHP 8.1 or older, what do you recommend and when can it be moved?
Some hosts patch older versions with builds from their own vendors, so the version number in Site Health may not tell the whole story. A clear written answer from the host is worth more than guessing.
3. Plan a move to a supported PHP version
If you’re on 8.1 or older, moving up is the real fix. Aim for 8.3 or newer rather than 8.2, given its end-of-life date.
Do this carefully. Older themes and plugins sometimes break on newer PHP, so the safest route is to test on a copy of the site first, or have your developer do it. Take a fresh backup before anything changes.
4. Update WordPress, the theme and plugins
Install WordPress 7.1.4, or the latest release for your branch if you’re on an older one. Then update the theme and every plugin. Delete any plugins and themes you no longer use, because inactive code can still be a way in.
5. Check for signs that someone got in
The NCSC specifically warned that attackers may have installed backdoors on unpatched servers, which would stay in place after the fix. Things worth checking:
- Users in WordPress you don’t recognise, especially administrators
- Pages, posts or links you didn’t add
- Your site redirecting visitors somewhere unexpected
- Warnings from Google Search Console or your browser
Most hosts can run a malware scan for you if you ask. If anything looks wrong, don’t just delete it: ask your host or a developer to investigate, because a backdoor is usually more than one file.
6. Make sure your backups are real
A backup stored on the same server as your website isn’t much use if the server is compromised. Check that copies are kept somewhere separate, and that someone has actually tried restoring one.
Should this make you leave WordPress?
Not automatically. A WordPress site with a responsive host, a sensible number of plugins and someone keeping it updated can be perfectly safe.
What PHP2Shell showed is how many separate parts a typical WordPress site depends on, and how a delay in any one of them leaves you exposed through no fault of your own. If your site is a brochure site that changes a few times a year, it may not need a PHP server at all. I’ve written up the options, and the full timeline with links to the original reporting, on the move off WordPress page.
If you’d like a second pair of eyes, my free website health check flags whether a site runs WordPress and which PHP version it’s on.
Sources
- PHP: Security advisory and security releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (21 October 2026)
- NCSC: Critical security issue affecting PHP
- BleepingComputer: PHP ships emergency patches for critical PHP2Shell flaws
- Il Sole 24 Ore: PHP2Shell, when a software vulnerability becomes a global emergency
- Al Jazeera: World leaders warn of security flaws found in PHP programming language
- IBTimes Singapore: Websites go dark worldwide as governments race to patch PHP2Shell
- WordPress.org: Version 7.1.4
- WordPress.org: Site Health screen
Filed under WordPress, Security, Small Business