NerdyData.com
SearchPricingSign Up
Sign Up


PHP2Shell: 1,406,086 Websites Advertise Their PHP Version

10/22/2026
Author: David Bielik
Copy Article Link
Share on TwitterShare on LinkedIn

On October 21, 2026, the PHP project shipped an emergency security release for two flaws in PHP core. Both let an attacker run code on your server without logging in, with the same permissions as your web server. Every PHP version back to 5.4 is affected.

NerdyData found 1,406,086 websites that tell every visitor which PHP version they run. Below is why you should patch today, and how to use NerdyData to find websites that are still advertising a vulnerable PHP version: your own forgotten servers, your clients' sites, or the vendors you depend on.

Why you should patch PHP2Shell right away

  • No login needed. Both bugs can be triggered by an unauthenticated request. CVSS v4.0 rates each one 9.2 out of 10.

  • It's in PHP itself, not a plugin. CVE-2026-109618 corrupts memory while PHP handles running out of memory. CVE-2026-109619 is a use-after-free in state PHP keeps between requests. Your application code doesn't need to have a bug.

  • Attacks started early. The CVE details leaked, the release was moved forward a day, and exploitation attempts were seen before the patch was public.

  • Apache mod_php is the most urgent. A demonstrated exploit triggers before your application code runs, so a web application firewall rule inside your app won't help.

  • Old versions stay vulnerable. PHP 8.1 and older are end of life. They get source backports only, no official release, so most of those servers will never be fixed by a routine update.

Fixed versions

BranchUpgrade toBranch status
PHP 8.58.5.12Supported
PHP 8.48.4.27Supported
PHP 8.38.3.36Security fixes only
PHP 8.28.2.35Security fixes only
PHP 8.1 and olderNone (source backports only)End of life

If you install PHP from your Linux distribution (Ubuntu, Debian, Red Hat), update through its package manager instead. Distributions backport the fix into their own builds without changing the PHP version number.

How to find websites running PHP

NerdyData crawls millions of websites and stores their page source, cookies and HTTP response headers. PHP leaves several fingerprints. Each search below links to live results.

Website counts as of October 22, 2026.

1. The X-Powered-By header: sites showing their PHP version

With expose_php = On, PHP's default, PHP adds a header like X-Powered-By: PHP/8.3.12 to every response. This is the most direct way to see a site's PHP version from outside. Since the fix only shipped on October 21, almost every site in this list was crawled on a vulnerable version.

Search: x-powered-by: PHP: 1,406,086 websites

2. The patch number

You can search for a full version string, for example the last vulnerable 8.4 release:

Search: x-powered-by: PHP/8.4.26: 11,923 websites

3. PHP 5: patch numbers 37 to 45

One case does isolate a branch. No PHP 7 or PHP 8 release has reached patch level 37, but PHP 5.4 ran to 5.4.45, PHP 5.5 to 5.5.38 and PHP 5.6 to 5.6.40. A site sending one of these patch numbers is on PHP 5, years past end of life:

Search: x-powered-by: PHP/5.6.40: 65,824 websites

Search: x-powered-by: PHP/5.5.38: 7,826 websites

Search: x-powered-by: PHP/5.4.45: 10,789 websites

Each search also matches the other PHP 5 releases with the same patch number (5.4.40 and 5.6.40, for example), so every result is on PHP 5. These three searches alone find 84,439 websites on PHP 5.

4. Linux distribution builds

Distribution packages add a build string to the version, and that string survives in our index. It tells you the operating system release and the PHP branch it ships:

SearchFindsWebsites
x-powered-by: PHP/8.1.2-1ubuntu2Ubuntu 22.04 LTS packages (PHP 8.1.2 plus Ubuntu patches)281
x-powered-by: PHP/7.4.3-4ubuntu2Ubuntu 20.04 LTS packages (PHP 7.4.3 plus Ubuntu patches)239
x-powered-by: PHP/7.2.24-0ubuntu0.18.04Ubuntu 18.04 LTS packages (PHP 7.2.24 plus Ubuntu patches)89
deb.sury.orgPackages from the popular Ondřej Surý repository for Debian and Ubuntu1,558

All three Ubuntu releases above ship a PHP branch that is end of life upstream. Whether a given server has the PHP2Shell fix depends on the package revision at the end of the header (the .20 in 8.1.2-1ubuntu2.20), so check your distribution's security tracker for the fixed revision.

5. PHP sites that hide their version

Many servers set expose_php = Off or strip the header at a proxy, so they send no version at all. You can still tell they run PHP, and every one of them should be checked:

Search: PHPSESSID (the default PHP session cookie): 582,491 websites

Search: x-powered-by: PleskLin (Plesk hosting on Linux, where most sites run PHP): 118,939 websites

Popular PHP applications are an even bigger signal. Our technology reports for WordPress, Drupal, Magento and Laravel list sites built on PHP whether or not they show a version.

Search from the command line

The same searches work through the NerdyData API and Project Discovery's Uncover, so you can feed the results into your own tools:

uncover -nerdydata 'x-powered-by: PHP' -f host -silent

What to do now

  1. Upgrade to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or install your distribution's patched package.

  2. If you run PHP 8.1 or older, plan the upgrade to a supported branch. Until then, apply the PHP security team's source backport or put the server behind a filtering proxy.

  3. Restart PHP-FPM or Apache after upgrading, so the old binary isn't still in memory.

  4. Set expose_php = Off. It won't fix anything, but it keeps your version out of lists like the ones above.

Frequently asked questions

What is PHP2Shell?

PHP2Shell is the name given to two critical vulnerabilities in PHP core, CVE-2026-109618 and CVE-2026-109619. Both allow unauthenticated remote code execution with the privileges of the web server process. One corrupts memory during out-of-memory handling, the other is a use-after-free in state kept between requests.

Which PHP versions are affected by CVE-2026-109618 and CVE-2026-109619?

Every PHP release back to PHP 5.4 is affected, up to and excluding the fixed releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35, published on October 21, 2026. PHP 8.1 and older are end of life and will not get an official release.

How do I check which PHP version my website runs?

Run php -v on the server, or call phpinfo() on a private page. From outside, the X-Powered-By response header often reveals it, for example X-Powered-By: PHP/8.3.12. That header is controlled by the expose_php setting, so a missing header does not mean the site is patched.

Does hiding the X-Powered-By header protect my site?

No. Setting expose_php = Off stops your site from advertising its version, which makes it harder to find, but the vulnerable code still runs. Upgrade PHP or install your distribution’s patched package.

Can NerdyData list every website running an exact PHP version?

Not always. NerdyData stores the X-Powered-By header, and 1,406,086 websites send one with a PHP version. But the search index splits version numbers on dots and drops single digits, so a search for PHP/8.4.26 also matches other branches ending in .26, such as 7.4.26 or 8.1.26. The patch number, distribution build strings and the PHP 5-only patch numbers 37 to 45 are still useful filters.

Is searching NerdyData for vulnerable PHP versions passive?

Yes. Searching reads data NerdyData has already crawled and never sends traffic to the matching websites. Scanning or testing those websites is not passive, so only test systems you own or have permission to test.