Why PHP2Shell won't be the last, and 5 things to do now
PHP2Shell was found with AI and fixed with help from volunteers. Why more flaws like it are coming, and 5 simple steps for small businesses.
By HackSpot team (Amethyst Apps) · · 4 min read

The short version: PHP2Shell wasn't a one-off. The flaws sat in PHP for years, AI tools helped find them, and the fixes reached millions of servers thanks to a small number of people, some of them volunteers. Experts expect more flaws like this, found faster. You can't stop that, but you can be ready: there are 5 simple things to do now.
What happened
On 21 October 2026 the PHP project fixed two critical flaws, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), both rated 9.2 out of 10. The UK's NCSC told organisations to act immediately. The day before, PHP had announced the release for 21 October at 14:00 UTC, but said it could release earlier if details became public. Details then leaked online, and the release was brought forward. Our PHP2Shell timeline has every date.
Why flaws like this keep happening
Much of the web runs on free, shared code. PHP is open source: anyone can use it for free, and it's looked after by the PHP project and the non-profit PHP Foundation. Getting the fixes onto servers also depends on people most businesses have never heard of.
The BBC told the story of Ondřej Surý, who has spent more than 20 years, largely in his spare time, packaging PHP for Debian and Ubuntu, two versions of Linux often used on web servers. When the flaws leaked, he dropped everything to turn the fixes into packages that website operators could install easily. He told the BBC he received more than $10,000 in donations in a few days, about a year's worth, and that big technology companies should do more: "If you just take and don't give back then it will backfire."
The code is old. The flaws went unnoticed for more than a decade, and Wiz, which found them, says every PHP version released in the last ten years is affected by at least one.
AI is finding bugs faster. The researchers used AI tools to find the flaws. "The underlying bugs weren't new; what changed was our ability to find them," cyber-security researcher Salil Kanhere told the BBC.
Why the next one is coming
Ondřej Surý put it plainly: because AI is getting better at finding security flaws, "this might not be an isolated incident", and "people should be prepared to act this quickly more often".
PHP2Shell also showed how little time there can be. Cloudflare's chief executive said it saw thousands of attempts to exploit the flaws in the 10 hours before they were announced, and Amazon said it was targeted days before the public disclosure, both according to the BBC. When the next one comes, the businesses that cope best will be the ones that already know who to call.
5 things to do now
- Know who looks after your website. Write down who hosts it, who your developer is, and how to reach them quickly. In a scare like this, the first job is a fast message to the right person.
- Make sure PHP gets patched, not just WordPress. The PHP2Shell fix has to be applied to PHP itself. Updating WordPress or its plugins doesn't fix it. Ask your host to confirm the PHP version, or send them our ready-made message.
- Run a free HackSpot check. Check your website to see what it shows the public, explained in plain English, with a message for whoever should fix each thing.
- Tick "Email me if this result changes". It's on your report. We'll re-check your website once a day and only email you if the result changes, so you hear about the next problem without having to remember to look.
- Keep an eye on your suppliers. Your booking system, payment provider or CRM may run PHP too. Watch their status pages and messages, and expect them to need updates as well. HackSpot can watch your suppliers for you.
Questions people ask
Is PHP still safe to use?
Yes, once it's updated. PHP is used by a huge share of the web, and the PHP project fixed these flaws quickly. What matters is that your website runs a fixed version: PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or later.
Does this mean my website has been hacked?
No. A flaw being found doesn't mean your site was attacked. Ask your host to confirm PHP has been updated, and check your website for free to see what it shows the public.
Do I need to pay for anything?
No. The PHP fixes are free. If someone else manages your hosting, ask them to apply them. HackSpot's check is free too.
More on PHP2Shell
- PHP2Shell: what small businesses need to do today
- PHP2Shell timeline: what happened and when
- How to check which PHP version your website runs
- When your suppliers go down
Sources
- The PHP developer who became the unsung hero of the internet, 25 October 2026 (BBC News)
- What is PHP and why did it spark a global cyber-security scramble?, 22 October 2026 (BBC News)
- Upcoming critical PHP security release, 20 October 2026 (php.net)
- PHP security advisory, 21 October 2026 (php.net)
- Critical security issue affecting PHP (NCSC)
- PHP2Shell research and timeline (Wiz)