All articles
Cyber security

PHP2Shell: what the critical PHP vulnerabilities mean for your business website

Published22 October 2026
Last updated22 October 2026
Reading time8 min read
AuthorJames Powell
In short

On 21 October 2026 the PHP project released emergency fixes for two critical vulnerabilities, nicknamed PHP2Shell. They are in PHP itself, not in a particular website or plugin, and researchers have shown they can allow an unauthenticated attacker to run code on a vulnerable server. PHP’s own advice is blunt: there are no complete mitigations, and updating is the only safe choice. If your website runs on PHP, which most do, the question for you is simple: has the PHP version on your server been updated, and who is responsible for checking?

What happened

The two flaws are tracked as CVE-2026-109618 and CVE-2026-109619, and both are rated 9.2 on the CVSS v4.0 scale, which is critical. Here is how the timeline unfolded, according to the security researchers involved and the PHP project:

  • 19 August: Wiz Research found the first bug, using AI tools as part of the process.
  • 24 August: Wiz reported the issues to the PHP security team.
  • 21 September: PHP acknowledged the reports.
  • 20 October: details of the flaws appeared online before the patches were ready, according to security firm Huntress, and PHP issued an advance notice of an emergency release.
  • 21 October: PHP released fixed versions and published its security advisory.
Timeline, 2026 From discovery to patch
  1. 19 AugWiz Research finds the first bug
  2. 24 AugReported to the PHP security team
  3. 21 SepPHP acknowledges the reports
  4. 20 OctDetails leak online before the patches
  5. 21 OctFixed versions released
Update PHP, then check it
As reported by the researchers involved and the PHP project.

The early leak matters because it shortened the time between “a flaw exists” and “everyone knows how it works”, which is exactly the window defenders want to keep as small as possible.

What the flaws actually are

In plain English, both relate to how PHP handles memory when something goes wrong, such as running out of memory while processing a web request.

  • CVE-2026-109618: when PHP runs out of memory part-way through setting up a request, it can be left with half-prepared data that its clean-up then treats as valid.
  • CVE-2026-109619: PHP can keep hold of information from one request after the memory behind it has been released, and a later request handled by the same worker can then use that stale information.

The researchers at Wiz demonstrated that these can be used for unauthenticated remote code execution, meaning an attacker with no login can run their own commands on the server, and for exposing the memory of the PHP process, which can contain passwords, tokens and API keys. PHP says the risk is highest for servers running PHP as an Apache module (mod_php), and that PHP serving web requests in other ways, such as PHP-FPM, also needs patching.

The key point for a business owner: because the flaw is in PHP itself, the application on top does not matter much. Wiz demonstrated attacks against current WordPress, Drupal and Joomla, and says that even a very simple site on an affected PHP version may be vulnerable. Updating a plugin or theme is not the fix. The PHP version running on the server is.

Is it being exploited?

This is the part that is still changing, so treat it as a snapshot from 22 October 2026. On 21 October, security firm watchTowr first reported no exploitation in the wild, then later that day said it was observing active exploitation attempts against both flaws. Cloudflare said it was seeing early attacks and that attackers were changing their payloads to get past its protections. Amazon Threat Intelligence reported an attempt on its honeypot on 17 October, four days before the fixes were public, and says it is unclear whether the attempts it saw would have worked against real systems. PHP itself has said an exploit exists for the Apache module setup, and unverified exploit code is circulating publicly. As of the sources we checked, none reported a confirmed break-in of a specific server, and neither flaw was yet listed in the US CISA catalogue of known exploited vulnerabilities. Some organisations took services offline as a precaution.

Whatever the exact state of play when you read this, the sensible assumption is that attackers are working on it. The situation tends to move quickly from “researchers have shown it” to “criminals are scanning for it”.

Who is affected

Any server running PHP to serve web pages. That is a very large group: according to W3Techs, PHP is used by 69.3% of websites whose server-side language is known (figure dated 22 October 2026). In practice this includes:

  • Websites built on WordPress, Drupal, Joomla or Magento
  • Shared hosting and hosting control panels
  • Some business software and appliances that quietly include their own copy of PHP

What the fix is

PHP released these fixed versions on 21 October 2026:

  • PHP 8.5.12
  • PHP 8.4.27
  • PHP 8.3.36
  • PHP 8.2.35

PHP 8.6.0 RC4 also contains the fixes. Some hosting providers and Linux distributions apply fixes to their own builds without changing the version number, so the number alone does not always tell you the full story. This is why you need to ask your provider rather than guess.

PHP has published some interim measures for servers that cannot be updated at once, but states clearly that they only reduce exposure to specific attack routes and do not make a server safe. They are a stopgap, not a plan.

The older versions problem

This is where many small businesses will find an uncomfortable answer. PHP 8.1 and older no longer receive updates from the PHP project. PHP says some distributions and long-term support vendors provide their own backported fixes, and it released minimal source backports for 8.1, 8.0 and 7.4 for people who build PHP themselves. If a site is on one of those versions, whether it is protected depends entirely on whether the hosting provider or vendor has supplied a fix.

Even the newer branches have a clock on them. PHP says version 8.2 reaches end of life on 31 December 2026. If your site is on 8.2 today, you are protected by this week’s update, but you should be planning your next upgrade now.

What to ask your web host or IT provider

You do not need to be technical. These questions will tell you where you stand:

  1. Which version of PHP does our website run on?
  2. Has it been updated since 21 October, and how do you know?
  3. If we are on PHP 8.1 or older, how are we protected, and what is the plan to move?
  4. Do we have any other software or appliances that include PHP?
  5. Do you monitor for signs that something has gone wrong, and when did you last check our backups restore?

If you run WordPress, your version of PHP is usually shown under Tools, then Site Health, then Info, in the Server section.

What we have done at i90

We have checked the PHP versions in use on our own hosting and on the websites we host or manage for clients. Where PHP needed updating, we have updated it to a fixed version, or confirmed with the hosting provider that the fix has been applied. We have also been in touch with clients, to let those who were affected know what we have done, and to reassure those who were not.

If you are not one of our clients and want a second pair of eyes on where you stand, get in touch.

If you think you may have been affected

If a server may already have been compromised, the advice from security firms is to isolate it, keep the web and PHP logs, and check for unexpected new files in the website folders, new scheduled tasks and new user accounts. Amazon Threat Intelligence, as reported by Tenable, recommends that any investigation looks back to 17 October, the date of the earliest attempt it saw. This is a job for your IT provider or hosting company. If you are not sure who that is, get in touch and we will point you in the right direction.

Common questions

Is my WordPress site affected by PHP2Shell?

If it runs on PHP, the flaws are in PHP itself, so it can be. Updating WordPress, a plugin or a theme is not enough on its own. The PHP version on the server needs to be updated to a fixed release, or your host needs to confirm it has applied the fix.

What is PHP2Shell?

It is the nickname for two critical vulnerabilities in PHP, tracked as CVE-2026-109618 and CVE-2026-109619, which PHP patched on 21 October 2026.

How do I check which PHP version my website uses?

Your hosting control panel or your web host can tell you. On WordPress, it is shown under Tools, then Site Health, then Info, in the Server section. If you are unsure, ask your host or IT provider.

My site runs on PHP 8.1. What should I do?

PHP 8.1 no longer gets updates from the PHP project, so protection depends on a fix supplied by your host or vendor. Ask them in writing whether they have applied one, and agree a plan to move to a supported version.

Should I panic?

No, but do not leave it either. Updating PHP is the answer, and for most businesses it is a job for your host or IT provider that takes little time. The risk is in nobody realising it needs doing.

Sources

Want a second pair of eyes?

If you want to know where you stand on PHP, get in touch and we will help you find out.

Get in touch