PHP2Shell: what last week's PHP flaw means for your business website
· 3 min read
Last Wednesday, the team behind PHP pushed out an emergency fix for two serious security holes. If you run a business website, there’s a good chance this affects you, even if you’ve never heard of PHP.
Here’s what’s going on in plain English, and what to do about it this week.
What’s happened
PHP is the software that runs behind most websites. WordPress is built on it, and roughly 7 in 10 websites use it.
On Wednesday 21 October, PHP released urgent fixes for two flaws that researchers have nicknamed PHP2Shell. Put simply, they let an attacker take control of the server your website runs on. No password, no login, nobody needs to click a dodgy link. The attacker just sends the right requests to your site.
Why this one is serious
Security flaws come out every week, and most don’t deserve a blog post. This one does, for four reasons.
- It’s in PHP itself, not your website. You can have the latest WordPress and every plugin up to date and still be exposed. The only fix is updating PHP.
- Attackers were quick. Attempts to use it were spotted before the fix was even released, and hosting companies were reporting real attacks on the morning it came out.
- Old versions aren’t getting a fix. PHP only patched the versions it still supports. Hundreds of thousands of websites are still on older versions, and for them no official fix is coming.
- It isn’t finished. Two days after the fix, PHP warned about a third, related problem. It’s much less likely to affect most sites, but it tells you people are still digging.
What it could mean for your business
Attacks like this aren’t personal. They’re automated, and they sweep across thousands of websites looking for any that haven’t been fixed. Small businesses get hit because they’re easy, not because anyone picked them.
If someone gets in, the usual results are:
- Your visitors get redirected to scam sites, often only on phones, so you might not notice for weeks.
- Card details get stolen from your checkout, if you take payments online.
- Customer details from your forms and orders get copied.
- Your website gets used to send spam, and your normal emails start landing in junk.
- Google warns people away from your site, and your host may take it offline.
If customer data is involved, you may also have to report it to the ICO within 72 hours.
What to do this week
- Ask one question. Email whoever looks after your website and ask: “Has our site had the PHP security fix from 21 October?” If they’re not sure, that’s your answer.
- Check your version if you can. In WordPress, go to Tools, then Site Health, then the Info tab, and open the Server section. If your PHP version starts with 7 or 5, or is 8.0 or 8.1, it’s no longer supported and needs upgrading, not just patching.
- If your site wasn’t fixed last week, have it checked. Ask for a look for signs of a break-in, not just an update. Fixing the hole doesn’t remove anyone who’s already got in.
One more thing. If you’re told there’s nothing to worry about because your site sits behind Cloudflare or a firewall, get a second opinion. Those help, but they don’t fix PHP.
If you’d like us to check your site, see our website security service or get in touch and we’ll tell you plainly where you stand.
For whoever manages your website
Forward this section to whoever manages your website.
- PHP2Shell is CVE-2026-109618 and CVE-2026-109619 (CVSS 4.0 score 9.2), unauthenticated remote code execution in the PHP runtime. Fixed in 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released 21 October 2026. Application, theme and plugin updates do not fix it.
- Backported builds from a distribution or host are fine if they include both CVEs. Please confirm against the package changelog, not the version string.
- PHP 8.1 and older got no upstream fix. PHP 8.2 security support ends 31 December 2026.
- CVE-2026-115560 is a related, narrower issue disclosed on 23 October that the October releases don’t fix. Until PHP ships a fix, it advises setting
session.upload_progress.enabled=0unless the site needs that feature. - A WAF in front of the site is a stopgap. Cloudflare’s own guidance is to patch PHP even with its rules enabled.