On 21 October 2026 the PHP project released fixes for two critical flaws, CVE-2026-109618 and CVE-2026-109619, now known as PHP2Shell. Either can let an attacker run their own code on a web server with a single request, without logging in. Both are rated 9.2 out of 10. The UK’s National Cyber Security Centre (NCSC) published an alert the same day telling every organisation that uses PHP to update.
If your business has a website, there’s a good chance this affects you. Here’s what it means in plain English, and what to do.
Does it affect my website?
PHP is the language behind a large share of the web. Every WordPress site runs on it, as do most cPanel hosting accounts and many small-business website builders and booking systems. The flaw is in PHP itself, not in your website’s code, so it affects every common way of running PHP: PHP-FPM, Apache with mod_php, php-cgi, LiteSpeed and FrankenPHP.
Updating WordPress, your theme or your plugins does not fix it. The PHP on the server has to be updated.
Which versions are safe?
- PHP 8.5.12 or later
- PHP 8.4.27 or later
- PHP 8.3.36 or later
- PHP 8.2.35 or later
PHP 8.1 and older are no longer supported. The PHP security team has published limited source fixes for 7.4, 8.0 and 8.1, but the right move is to get onto a supported version. Some hosts and Linux distributions patch older version numbers themselves, so if your version looks old, ask your host before assuming the worst.
Is anyone actually attacking this?
Yes. Amazon’s threat intelligence team recorded an exploitation attempt on 17 October, four days before the flaws were made public, and Cloudflare has reported attack traffic since. Researchers have also shown that the flaws can leak the contents of the server’s memory, which can include passwords, tokens and API keys. On the day of the alert, several UK council websites and the Metropolitan Police website were reported offline.
What to do today
- Find out your PHP version. In cPanel, look for “Select PHP Version” or “MultiPHP Manager”. On managed hosting, email your host and ask: “Which PHP version does my site run, and does it include the PHP2Shell fix?”
- Update PHP to one of the versions above, then make sure PHP is restarted. A patch that’s installed but not running doesn’t protect you.
- If you can’t update today, ask your host to apply the PHP project’s temporary mitigations and to put a web application firewall in front of the site. Cloudflare has added rules for known attack patterns, including on its free plan. These buy time; they don’t replace the update.
- If neither is possible, the NCSC’s advice is to consider taking the site offline until it’s fixed.
- After patching, look for signs that someone got in first: admin accounts you don’t recognise, new plugins, files changed recently. Change your hosting, WordPress and email passwords, and any API keys stored on the site. If you find anything suspicious, get professional incident response help rather than cleaning up on your own.
Why this keeps happening, and why it’s getting faster
PHP2Shell won’t be the last flaw like this. The NCSC’s assessment of AI and cyber threat puts it bluntly:
“The time between disclosure and exploitation has shrunk to days and AI will almost certainly reduce this further.”
For a small business, that means a website can’t be something you launch and forget. Someone has to be watching: applying updates when they land, checking the site every week, and acting quickly when an alert like this goes out. Attackers use automation and AI to find vulnerable sites; the same tools, used properly, are how you stay ahead of them.
How we can help
- Score your website free. If your site announces its PHP version, the instant score tells you straight away whether it’s an affected one.
- Data and security foundations: a security quick check, a fix list in plain English, and the fixes done at a fixed price.
- Hosting with JMS: PHP updates applied for you, daily backups, and a weekly health report on your site.
- Website Watch: a free check of your website every month, with one fix explained simply.
This article is general guidance, not a substitute for advice on your own systems. If you think your site has been compromised, treat it as an incident and get help quickly.
Questions people ask
Is my WordPress site affected by PHP2Shell?
WordPress runs on PHP, so it is affected unless the PHP on your server has been updated to a fixed version (8.2.35, 8.3.36, 8.4.27 or 8.5.12 or later) or your host has applied a back-ported fix. Updating WordPress or its plugins does not fix it: the flaw is in PHP itself.
How do I check my PHP version?
In cPanel, look for “Select PHP Version” or “MultiPHP Manager”. On managed hosting, ask your host which PHP version your site runs and whether it includes the October 2026 PHP2Shell fix.
What if my host can’t update PHP straight away?
Ask them to apply the PHP project’s temporary mitigations and put a web application firewall in front of the site. If neither is possible, the NCSC advises considering taking the system offline until it is fixed.
Sources
- NCSC: Critical security issue affecting PHP (21 October 2026)
- Help Net Security: PHP2Shell, critical PHP vulnerabilities patched (21 October 2026)
- Qualys: PHP announces critical security release for two vulnerabilities (20 October 2026)
- Insurance Business UK: councils and Met Police among sites pulled offline after NCSC alert
- NCSC: Impact of AI on cyber threat from now to 2027 (May 2025)