Free tools · Security

PHP2Shell check

On 21 October 2026 two serious vulnerabilities in PHP were disclosed and fixed straight away. Does your website run on PHP (for example WordPress, WooCommerce or Laravel)? Check in two steps whether your server has been updated: first a quick check from the outside, then, if you like, the exact version with our check file.

Step 1 · Quick check · indication

What does your website show from the outside?

Enter an address. We request the homepage once, just like a browser, and look at the headers and the HTML to see whether PHP is running and whether the server reveals its version.

This is an indication. Most servers hide their PHP version (good), and a version number in the headers may come from a proxy. Do you see "version unknown", or are you in doubt? Then continue to step 2.

We only make a normal page request for your homepage, just like a browser, and read the headers and the HTML. No attacks, no scans. Without an email address we store nothing.

Step 2 · Verified check · exact version

Know for sure which PHP version your site uses

With our small check file on your site we read the exact PHP version, plus the server type (for example PHP-FPM) and your Linux distribution. The file shows nothing else: no phpinfo, no paths, no passwords, no shell commands. Every file has its own token, so we can see that the response really comes from your file.

  1. 1

    Download

    Download php2shell-check.php with the button below. You get a file with your own token.

  2. 2

    Upload

    Put it in the root folder of your site (e.g. public_html) via FTP or your hosting control panel.

  3. 3

    Check

    Enter your website and click Check. We only request yoursite.com/php2shell-check.php.

  4. 4

    Delete again

    Remove the file straight away and click 'Check whether the file is gone'.

1. Download php2shell-check.php

Small text file, open and readable. Feel free to look at it in a text editor first.

3. Check your site

You see the exact version, whether it contains the fix (patched, vulnerable or outdated branch), the server type and your distribution.

What we cannot see: backports from your distribution or hosting provider. Debian, Ubuntu, Red Hat and AlmaLinux often include fixes without raising the PHP number. If a distribution package is detected, we point you to that distribution's security page. You can only be sure about that with access to your server.

Prefer not to let us fetch anything? Open the file in your browser yourself (yoursite.com/php2shell-check.php): it shows the same result.

We only request this one address: https://yourcompany.com/php2shell-check.php

Tip: do not let your server show its PHP version. Set expose_php = Off in php.ini (or ask your hosting provider to do so). It does not fix PHP2Shell, but it makes things harder for attackers.

What is going on?

PHP2Shell consists of two vulnerabilities: CVE-2026-109618 and CVE-2026-109619, with a severity score of 9.2 (CVSS v4). In plain language: if PHP runs out of memory at an unfortunate moment, or if old data from a previous visit is left behind, an attacker can in certain cases run their own code on your server.

The vulnerable code has been in PHP since version 5.4.0 and applies to both mod_php and PHP-FPM. According to the PHP team no setting fully solves it: updating is the solution.

Patched versions

PHP 8.2.35+PHP 8.3.36+PHP 8.4.27+PHP 8.5.12+

PHP 8.1 and older no longer receive official support. For 7.4, 8.0 and 8.1 only minimal source backports were released. Distributions (Debian, Ubuntu, Red Hat, AlmaLinux) ship their own backports with their own version numbering. Upgrading to 8.2 or newer remains the advice.

How big is the risk? Sansec reported on 22 October that the public exploits do not work against a standard PHP installation, which makes mass exploitation less likely. Amazon did observe an attack attempt as early as 17 October. In short: no panic, but do update.

Sources: Sansec · Help Net Security · php.net

Frequently asked questions

What is PHP2Shell?

PHP2Shell is the name for two serious vulnerabilities in PHP, disclosed and patched on 21 October 2026: CVE-2026-109618 and CVE-2026-109619 (CVSS 9.2). In certain situations an attacker can use them to run their own code on the server. It applies to both mod_php and PHP-FPM.

Which PHP versions are patched against PHP2Shell?

PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12 (and newer) contain the fix. PHP 8.1 and older no longer receive official support; for 7.4, 8.0 and 8.1 the PHP team only released minimal source backports. Hosting providers and distributions may ship their own backports, so for older versions the version number does not tell the whole story.

Can I fix PHP2Shell with a setting?

No. According to the PHP team, no configuration change fully solves the problem. Updating to a patched PHP version is the solution. Hiding your PHP version (expose_php = Off) is sensible, but it is not a fix.

How does the verified check work?

You download a small PHP file with its own unique token and put it in the root folder of your site. Our server then requests only that one address (yoursite.com/php2shell-check.php) and gets back the exact PHP version, the server type (SAPI) and the name of your Linux distribution. The token tells us that the response really comes from your file. Afterwards you delete the file again; with one click you can check that it is gone.

My server runs Ubuntu, Debian or AlmaLinux. Is the version number enough?

Not always. Distributions such as Debian, Ubuntu, Red Hat and AlmaLinux often include security fixes in their own PHP packages without raising the PHP number (backports). A lower number may therefore still be patched. We show which version is running and link to your distribution's security page; whether the fix is in your package can only be seen there or with access to your server.

How big is the risk at the moment?

Security company Sansec reported on 22 October that the public exploits do not work against a standard PHP installation, which makes mass exploitation less likely. Amazon did observe an attack attempt as early as 17 October. Updating therefore remains important.

Need help updating?

Not sure how to update PHP, or does your site run on an old version that cannot simply be upgraded? We are happy to take a look with you, without obligation.

Get in touch