Opens in a new tab
DUNFERMLINE · FIFE · EDINBURGH · SCOTLAND
Free website review

PHP2Shell: the critical PHP flaws affecting millions of websites

Two critical PHP flaws, known as PHP2Shell, affect websites all over the world. Here's what they are, what we did on 20 and 21 October, and what it means for your website.

Software flaw news, a code window with a warning sign illustration
CategoryCyber security
Published22 October 2026
Reading timeA few minutes
Written byUniversal Computing

On 21 October 2026, the PHP project fixed two critical flaws in PHP, the programming language most websites run on. Known together as PHP2Shell, they could let an attacker run commands on a web server without logging in. They affect PHP websites all over the world, whoever built or hosts them. Every website we manage was running the fixed versions of PHP the same day.

What PHP2Shell is

PHP2Shell is the name given to two vulnerabilities in PHP itself, CVE-2026-109618 and CVE-2026-109619. The PHP security team rates both critical, at 9.2 out of 10 on the CVSS v4.0 scale.

Both are memory errors in the way PHP tidies up after a web request. One is triggered when PHP runs out of memory mid-request. The other leaves old data behind that a later request can pick up. Either way, a specially crafted request could let an attacker run their own code on the server, with no password needed.

Researchers at Calif, Wiz and OpenAI found the flaws, BleepingComputer reports. Calif traced the oldest affected code to PHP 5.4, released in 2012.

The PHP team gave advance notice of the fix on 20 October. It released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on 21 October, and says “updating is the only safe choice”.

Attacks started before the fix came out. Amazon says its decoy servers recorded an attempt to exploit PHP2Shell on 17 October, four days before the flaws were made public. Cloudflare’s chief technology officer also said it was seeing early attacks ahead of the patches, BleepingComputer reports. On 21 October, Amazon said PHP2Shell was “now being broadly exploited in the wild”. It added that it’s unclear whether any of these attempts would have worked on real-world systems.

PHP 8.1 and older versions no longer get new releases from the PHP project. Some Linux vendors and paid support services offer fixes for older versions, but moving to a supported version is the long-term answer.

A worldwide issue

PHP is used by 69.3% of the websites whose server-side language is known, according to W3Techs on 22 October 2026. WordPress, Drupal and Joomla all run on it. Calif confirmed the attack on WordPress 7.1.2, Drupal 11.4.3 and Joomla 6.1.4. Because the flaws are in PHP itself, updating WordPress or its plugins doesn’t fix them.

BleepingComputer reports a VirusTotal estimate that more than 5.1 million PHP servers can be reached from the internet. One server can host many websites.

The UK’s National Cyber Security Centre says organisations using any version of PHP are affected, and advises them to update straight away. Every web host and business with a PHP website needs to make sure it’s updated, whoever built the site.

What we’ve done

We started work on 20 October, the day the PHP team gave notice.

  • 20 October. We took preventative action across our hosting platform to reduce the risk until the fix arrived.
  • 21 October. We installed the patched versions of PHP 8.2, 8.3, 8.4 and 8.5 on every website we manage, on the day they were released.
  • After the update. We tested every website to check it still works as it should. Where an older website wasn’t working correctly, we emailed its owner to talk through the options.
  • Now. We’re monitoring every website on our care plans.

What this means for you

If your website is on one of our care plans, you don’t need to do anything unless we’ve emailed you about it. Websites on our Care Plan and Growth Care Plan are our priority. Each one is on a patched version of PHP, has been checked to make sure it still works and is being monitored.

If we manage your website, it’s on a patched version of PHP too. If it wasn’t working correctly after the update, we’ve already emailed you.

If your website is hosted somewhere else, ask your host or developer to confirm the PHP2Shell fix is installed. In the PHP project’s own releases, the fix is in 8.2.35, 8.3.36, 8.4.27, 8.5.12 and later. Some Linux vendors add the fix to older-looking version numbers, so the number alone may not tell you. Attacks began before the fix, so ask them to check for signs of a break-in since 17 October too. If it can’t be updated quickly and the temporary workarounds can’t be used, the NCSC says to consider taking it offline.

Your questions

Is this only a problem with websites you’ve built?

No. The flaws are in PHP itself, so they affect PHP websites everywhere, whoever built or hosts them.

Do I need to do anything?

If we manage your website, only if we’ve emailed you about it. Not sure? Open a support ticket and we’ll check.

My website is quite old. What happens now?

A website built for PHP 8.1 or older may need some work to run on a supported version. If yours is one of them, we’ll talk you through the options. PHP 8.2 stops getting security fixes after 31 December 2026, so websites on 8.2 will need moving to a newer version by then.

Get your website checked

If you’re a client, open a support ticket or call 01383 840808. If your website is hosted somewhere else, book a free hosting health check and we’ll tell you where it stands. To keep your website patched and monitored, see our care plans and cybersecurity services.

Sources

WHAT IT MEANS FOR YOU

Questions about how this affects your business?

Book a free Business Technology Review: about 30 minutes, online or at your office. We'll look at your security, email and devices, and tell you plainly what's worth doing.