PHP2Shell: what the biggest PHP security scare in years means for your website
October 23, 2026 Posted by Sean Walsh Round-Up 0 thoughts on “PHP2Shell: what the biggest PHP security scare in years means for your website”This week, two critical flaws in PHP, the programming language that quietly runs most of the web, put website owners, hosts and governments on high alert. The issue was nicknamed PHP2Shell, and it was serious enough for the UK National Cyber Security Centre to issue an alert and for some organisations to take their websites offline as a precaution.
If you run a WordPress or WooCommerce site, this affected you, whether or not you heard about it. Here is a plain-English guide to what happened, why it matters commercially, and what you should check now.
What actually happened
PHP2Shell is the name given to two vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619. Both are rated 9.2 out of 10 for severity. In simple terms, they could let an attacker run their own commands on a web server without logging in, using a single specially crafted request that lands before any of the website’s own code runs.
The timeline moved quickly:
- 17 October: Amazon’s threat intelligence team recorded an attempt to exploit the flaw, four days before it was made public.
- 20 October: details leaked online ahead of the planned disclosure date. PHP brought its fix forward and warned everyone to prepare.
- 21 October, 15:00 UK time: PHP released patched versions (8.5.12, 8.4.27, 8.3.36 and 8.2.35). Cloudflare had already switched on firewall rules for its customers in the early hours.
- 21 to 22 October: security firms reported active exploitation attempts. The NCSC published its alert and priority actions for UK organisations.
The flaws were found and reported by researchers at Wiz, Calif and OpenAI’s Codex Security team. At the time of writing, no confirmed successful break-in had been reported, but attackers were clearly trying.
Why this matters if you are not a developer
PHP is used by around 69% of all websites whose server-side language is known, according to W3Techs. That includes every WordPress site, every WooCommerce shop and a long list of booking systems, CRMs and plugins that sit behind them.
For a business, a compromised website is not just an IT problem. It can mean:
- Malicious redirects or spam pages that Google flags, which can wipe out rankings and organic traffic for weeks.
- Stolen customer or patient data, with the regulatory and reputational fallout that follows.
- Broken checkouts and lost sales, particularly painful in the run-up to Black Friday.
- Paid campaigns sending budget to a site that is down or blocked by browsers.
The scale of the concern was clear from the response. In the Netherlands, several government services, including DigiD and MijnOverheid, were taken offline as a precaution. HR software provider BambooHR did the same across several countries.
The part most people miss: updating WordPress does not fix it
This is the key point for marketing teams. PHP2Shell sits in the server software underneath your website, not in WordPress, your theme or your plugins. Clicking “update” in your WordPress dashboard does nothing here.
The fix has to come from whoever manages your server: your hosting provider, your developer or your IT team. They need to update PHP, restart it properly and, ideally, put a web application firewall in front of the site. If you are on budget shared hosting, or on a server nobody has looked at in a while, that is exactly where the risk sits.
Sites running old, unsupported versions of PHP (8.1 and earlier) are in a weaker position again, because official updates for those versions have ended and fixes rely on backports from vendors.
What you should check now
Use this as a quick checklist with your host or developer:
- Confirm PHP has been patched. Ask your host for written confirmation that your server is on a fixed version, or has the vendor backport applied.
- Check your PHP version is supported. If you are on PHP 8.1 or older, plan an upgrade. It is overdue regardless of this incident.
- Ask about a firewall. A web application firewall (WAF) through a provider such as Cloudflare blocked many attack attempts before the patch existed.
- Know where your backups are. You want daily, off-site backups that you can restore quickly, not a single copy on the same server.
- Watch for warning signs. Unexpected 500 errors, new admin users, odd pages in Google Search Console or sudden traffic drops are worth investigating straight away.
- Follow the NCSC guidance. Its alert on PHP2Shell sets out priority actions, including taking systems offline if they cannot be fixed quickly.
How we handled it for our clients
For the sites we manage, our managed host WP Engine applied the PHP patch across its platform overnight on 21 October and added protective rules at the network edge through Cloudflare and Fastly while the rollout happened. We contacted clients the same day, explained what was happening in plain terms, and confirmed once the patch was in place.
Just as important was what was already in place before the news broke: daily backups, a private code repository and locally saved theme files. That is the difference between a stressful afternoon and a genuine crisis.
The bigger lesson: security is now part of performance
PHP2Shell is a reminder that your website’s security is tied directly to its commercial performance. Rankings, conversion rates and paid media returns all depend on a site that stays online and trusted. The businesses that came through this week calmly were the ones with managed hosting, a firewall, tested backups and a partner who knew who to call.
If you are not sure how your own site is set up, now is a good time to find out, before the next one.




