Security · 2026-10-25 · 6 min

PHP2Shell: what this week's PHP flaw means for your website

On 21 October the PHP project shipped emergency updates for two critical flaws, together called PHP2Shell. PHP runs underneath a great many websites, including every WordPress site and many web shops and customer portals. This article is for the owner or IT lead of a small or medium-sized business who wants to know whether the flaw affects their business, and what needs to happen now.

What is going on

The flaws are CVE-2026-109618 and CVE-2026-109619, both with a CVSS score of 9.2 out of 10. Either one lets an attacker without an account run code on the web server. The first is in how PHP handles running out of memory while reading a form or upload. In the second, data from an earlier request lingers and a later request reuses it.

According to the PHP security team the risk is highest for Apache with mod_php. There it has been shown that a single request without logging in is enough, before your website's own code even runs. So a login screen, a plug-in or a change to your own code does not stop it. PHP-FPM, php-cgi, FrankenPHP and LiteSpeed are vulnerable too, which covers almost every server that builds web pages with PHP.

Public technical details and proof-of-concept attacks are circulating. Security firm watchTowr reports seeing attacks on its honeypots since 21 October. The US agency CISA had not yet observed successful exploitation at that point. Assume that vulnerable servers are actively being searched for.

On 23 October PHP disclosed a third flaw, CVE-2026-115560. According to PHP it only affects unusually configured applications. There will be no emergency update; PHP advises turning off the session upload progress setting until the next regular release.

Does it affect your business?

Probably, if you have a website, web shop or customer portal that runs on PHP. That includes WordPress and WooCommerce, Magento, Drupal and Joomla, and a lot of custom software. Vendor software that ships with PHP, for example for a web interface, can be vulnerable too. Check with the vendor.

All versions before PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 are vulnerable. PHP 8.1 and older no longer receive updates from the PHP project. For those, only source code changes have been published, which a hosting provider or vendor has to build in themselves.

If your site runs with a hosting provider, they usually apply the update. Do not assume so without asking.

What to do now

  • List everything that runs PHP: websites, web shops, portals, test environments that are still online, and vendor software with a web interface.
  • Ask your hosting provider or web developer in writing: does our site run on a version with the fix (8.5.12, 8.4.27, 8.3.36 or 8.2.35, or a Linux distribution update with the fix), and were the PHP processes restarted afterwards?
  • If you run PHP 8.1 or older, have it upgraded as soon as possible. If an update cannot happen right away, take the site offline until it is fixed. That is what CERT-EU and CISA advise.
  • If you have to wait for the update, ask for the interim measures from the CERT-EU advisory, such as turning off session upload progress. They reduce the risk but do not remove it. Only the update does.
  • Have the log files checked for signs of abuse, such as an unusual number of memory errors ("Allowed memory size") or a web server starting commands on the server. When in doubt, treat it as an incident.
  • If personal data was taken in an attack, it may be a data breach. In the Netherlands the 72-hour notification term with the Autoriteit Persoonsgegevens then applies, from the moment you become aware of it.

What an outside scan can and cannot see

Many websites tell every visitor which PHP version they run, for example in the X-Powered-By header. An outside scan sees that. A visible version number helps an attacker search in a targeted way, and your web developer can usually hide it easily.

What an outside scan cannot establish is whether your server has already been fixed. Hosting providers and Linux distributions often apply fixes without changing the version number. So an old number does not always mean the server is vulnerable, and a hidden number does not mean the update is in place. You only get certainty by asking, or by checking from the inside.

How Axon Factory can help

AxonScan shows in a few minutes what your website and domain reveal from the outside, including visible software and versions, with who can fix each point: your web developer, your IT partner or yourself. For a PHP version taken from the headers, AxonScan deliberately does not say whether it is vulnerable, for the reason above. The report does give you a concrete start for the conversation with your hosting provider.

In a security audit an Axon Factory consultant looks further than the scan: which systems run PHP, how updates are arranged, who is responsible at your hosting provider or web developer, and whether the update has actually been applied. We do this together with your IT partner or hosting provider, and we agree beforehand what we look at.

There will be a next flaw, that much is certain. So record who keeps track of updates in your business, within how many days a critical update must be applied and how you check that with vendors. We can help with that too.

Sources

  • PHP project: security release of 21 October 2026 (8.5.12, 8.4.27, 8.3.36 and 8.2.35).
  • CERT-EU Security Advisory 2026-018, version 1.2 of 23 October 2026.
  • CISA: Critical Vulnerabilities in PHP Require Immediate Patching, 21 October 2026, updated 23 October.
  • Datadog Security Labs: PHP2Shell, critical vulnerabilities in PHP, updated 23 October 2026.
  • watchTowr: PHP2Shell FAQ.

This article describes the situation on 25 October 2026. Things can change quickly; for the current state, follow the advice of the PHP project and your national cyber security centre. If you see signs that your server has been attacked, bring in your hosting provider or IT partner straight away.

PRODUCT
AxonScan

AxonScan shows which software and versions your website reveals to visitors, alongside your email settings, https and privacy indicators. One-off €49 excl. VAT, refunded after an advice call.

View AxonScan →