“On 21 October the “PHP project” released emergency updates for two critical vulnerabilities in PHP itself.
That’s the programming language behind most of the world’s websites.
You might familar with some of the following PHP-based systems: WordPress, Drupal, and Joomla. Tracked as CVE-2026-109618 and CVE-2026-109619 and nicknamed PHP2Shell, they can let an attacker run code on a web server without logging in.
New Zealand’s National Cyber Security Centre (NCSC) issued an alert the next morning. It said it was aware of reports of active exploitation and urged organisations to patch as soon as possible. In the US, the Cybersecurity and Infrastructure Security Agency (CISA) told organisations to patch immediately, although as of its 23 October update it had not observed successful exploitation. (We sent out a warning that same morning, as soon as we became aware of the situation.)
Uptake here has been slow. On 22 October the NZ Herald reported a consultant’s estimate that nearly nine out of ten New Zealand websites had yet to patch.
What’s affected
The bugs are in PHP’s core engine, not in any particular website, theme or plugin. The PHP project says every PHP installation that serves web requests is at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. Wiz Research, which found the flaws, says every PHP version released in the last decade is affected by at least one of them, going back to PHP 5.4. Its researchers demonstrated pre-login takeovers of WordPress, Drupal and Joomla using the latest versions of each, and say even a basic “Hello World” page on a vulnerable PHP version can be exploited. Separately, they showed an attacker could read chunks of server memory containing passwords, tokens and API keys without taking over the server at all.
The NCSC adds that PHP is also built into firewalls, edge devices and other embedded platforms, and those may need their own assessment and patches from the vendor.
Found with AI
The underlying bugs, which come down to how PHP cleans up after running out of memory partway through a request, had been in the code for more than a decade. Wiz used frontier AI models from Google and OpenAI throughout the research. Its timeline shows the first vulnerability was found on 19 August, a working attack on WordPress was confirmed two days later, and the issues were reported to PHP on 24 August. By Wiz’s account, one researcher with AI completed in a week what would previously have taken a world-class team months. The company’s warning is that attackers have the same shortcut, and that flaws once too complex to be worth exploiting are now realistic targets.
What to do
The fix is to update PHP to version 8.5.12, 8.4.27, 8.3.36 or 8.2.35. PHP 8.1 and older no longer get updates from the PHP project. It has published minimal source backports for 7.4, 8.0 and 8.1, and some Linux distributions and long-term support vendors offer their own fixes.
For most businesses, the practical steps are:
- Find out where PHP runs. Your website is the obvious one, but CISA notes PHP is often a component of other software, so check intranets, customer portals, booking systems and network appliances too.
- If a hosting provider or web developer looks after your site, ask them to confirm in writing which PHP version it is now running. It is unusual for MSPs like Kinetics to manage these updates as the web people prefer to look after it for their clients.
- Patch internet-facing systems first. CISA says anything that can’t be updated, including servers still on PHP 8.1 or earlier, should be taken offline until it can be.
- Check anything that was exposed before patching for signs of compromise, as the NCSC recommends.
