If your business has a website, there is a good chance it runs on PHP, the programming language behind WordPress and many other sites. In October 2026 the PHP project fixed two critical flaws, nicknamed "php2shell", that could let an attacker take control of the server running a website without logging in. US officials have since listed them as exploited.

Most small businesses do not run their own web server, so the fix is in someone else's hands. The most useful thing you can do is ask the right questions.

What happened

On 21 October 2026 the PHP project released versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing two vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Both can allow unauthenticated remote code execution: an attacker on the internet could run their own commands on the server, much like a stranger getting a key to your shop and the till.

PHP's advisory says the risk applies to all PHP installations serving web requests, including common set-ups such as PHP-FPM, Apache with mod_php and LiteSpeed, and that "updating is the only safe choice". PHP 8.1 and older no longer get updates from the project; its security team published minimal source fixes for 7.4, 8.0 and 8.1, and some Linux vendors provide backported packages.

The UK NCSC published advice the same day, asking organisations to find their PHP systems, update internet-facing ones first and, if they cannot update or mitigate, to "consider taking the system offline until it can be fully mitigated."

On 26 October, CISA, the US cyber security agency, added both flaws to its Known Exploited Vulnerabilities (KEV) catalogue, which lists flaws with evidence of exploitation. It gave US federal agencies until 29 October to act. The Record reported that CISA's definition of exploitation includes attempts as well as successful attacks, and that many security companies had seen failed attempts. NCSC New Zealand said it was "aware of reports of active exploitation".

Why it matters

PHP is everywhere, often out of sight: in content management systems, online shops, booking tools and the control panels of hosting services. A business owner may not know their site uses it at all.

Patching also does not undo a break-in. As NCSC New Zealand put it, "Patching the exposed services will not remove already exploited systems." A site that was attacked before the update could still contain a hidden way back in.

Finally, old sites are the weak spot. Websites built years ago and left alone are the most likely to run an unsupported PHP version that will not get the official fix.

What it means for you

At home: nothing to do as a visitor. NCSC New Zealand says people simply browsing the internet do not need to take any action.

If you run a small business: NCSC New Zealand's advice is that "the first step is to contact your website developer, IT provider or hosting company." Ask them:

  1. Does our website or any online service we use run on PHP?
  2. Has the latest PHP security update been applied, and which version are we on?
  3. Did you check for signs of compromise from before the update?
  4. If the update cannot be applied yet, what temporary measures are in place?
  5. Is our PHP version still supported, and if not, what is the plan to move?

Get the answers in writing. If your site is old and nobody looks after it, consider taking it offline until it is fixed.

If you work in IT or at an MSP:

  1. Inventory every PHP install across clients, including PHP bundled inside appliances and third-party products, and patch internet-facing systems first.
  2. Follow CISA's alert and the NCSC's guidance: if you cannot update or mitigate a system, take it offline until it is fixed.
  3. Look for signs of compromise, such as PHP worker processes starting shells or downloading tools.
  4. Plan upgrades away from PHP 8.1 and older; PHP says 8.2 itself reaches end of life on 31 December 2026.

The bottom line

The php2shell flaws affect one of the most widely used pieces of web software, and the fix is already out. For small businesses the job is not technical: ask your web host or developer whether the update is in, whether they checked for a break-in, and what happens to sites running old versions.

This article summarises and comments on the sources listed below. It is general information, not legal or professional advice.