Experienced an incident?
Dasenda
Get an assessment
CareersPress kit
Part ofDordio & Associates

© 2026 Dasenda

PHP2Shell exposure checker

Determine whether your public web servers run an affected PHP version. The scan compares the version published by the server with the fixed releases.

  • CVE-2026-109618
  • CVE-2026-109619
php2shell-check
Scan type

Scope of each scan

Both modes are limited to GET requests identified by the Dasenda user agent and visible in server logs. No multipart forms are sent, as these are the attack vector for these vulnerabilities.

Domain home page
Basic · Yes
Deep · Yes
Response headers and HTML
Basic · Yes
Deep · Yes
Identification of WordPress, Drupal, Joomla, PrestaShop and Magento
Basic · Yes
Deep · Yes
Common subdomains
Basic · No
Deep · www, blog, shop, tienda, portal
Known paths
Basic · No
Deep · /index.php, /phpinfo.php, /info.php, /wp-login.php
Maximum requests
Basic · 6
Deep · 40
Authorisation required
Basic · Declaration
Deep · Declaration and DNS TXT record

Critical vulnerabilities in the PHP core

PHP2Shell comprises two unauthenticated remote code execution vulnerabilities. They are exploited through web requests before the application runs, so application access controls do not mitigate them. The PHP project released patches on 21 October 2026 and active exploitation has been confirmed.

Status as of 1 November 2026

  • PHP 8.5

    8.5.12

    Supported

  • PHP 8.4

    8.4.27

    Supported

  • PHP 8.3

    8.3.36

    Security fixes only

  • PHP 8.2

    8.2.35

    Security fixes only until 31 December 2026

  • PHP 8.1 and earlier

    No official release

    Unsupported and affected

Recommended remediation

  1. Update PHP

    Install the fixed release for your branch or your distribution's patched package. For distribution packages, consult the vendor's security advisory, as the version number may not reflect the patch. Updating is the only complete fix.

    Installed version

    php -v

    Debian and Ubuntu

    sudo apt update && sudo apt install --only-upgrade 'php*'

    RHEL, Rocky and AlmaLinux

    sudo dnf upgrade 'php*'
  2. Restart processes

    The patch does not take effect until PHP-FPM or the web server is restarted. Then confirm the version serving requests.

    sudo systemctl restart php*-fpm
    sudo systemctl restart apache2 nginx
  3. Rebuild containers

    Images include their own PHP version. Rebuild them on an updated base image and redeploy.

  4. Migrate unsupported versions

    PHP 8.1 and earlier have no official fixed release. Plan the migration to a supported branch and, in the interim, apply patches from your distribution or an extended support vendor.

  5. Apply temporary mitigations

    Limit request size and field count at the proxy, block multipart if the application does not use it and disable session upload progress. These measures are partial and none covers both vulnerabilities.

    php.ini

    session.upload_progress.enabled = Off

Frequently asked questions

What is PHP2Shell?
PHP2Shell is the name given to two critical vulnerabilities in the PHP core, published in October 2026. They allow unauthenticated remote code execution and affect all environments serving PHP on the web, including PHP-FPM, mod_php, php-cgi, FrankenPHP and LiteSpeed.
Can the scan affect server availability?
The checker performs GET requests only, in limited numbers and sequentially. It does not send exploits or trigger memory error conditions.
Does a result with no findings guarantee that the server is not vulnerable?
No. The checker evaluates the information the server publishes. A CDN, a reverse proxy or a hidden version can prevent detection, and internal servers are out of scope. Confirmation must take place on the server itself.
Why does the deep scan require a DNS record?
The deep scan examines paths and subdomains, so Dasenda requires proof of domain control. The requester publishes a TXT record and the scan runs once it is confirmed. Removing the record revokes access.
Can another organisation's domain be scanned?
Only by the domain owner or with the owner's express authorisation. Scanning third-party systems without authorisation can have legal consequences. Each request is logged together with the accepted declaration.
What data does Dasenda log?
Dasenda logs the domain, the scan type, the result, the date and an identifier derived from the requester's IP address. It does not store the content of the scanned site.
Does Dasenda provide remediation support?
Yes. Dasenda can inventory affected servers, apply updates and determine whether a compromise occurred before remediation.

Assess your organisation's full exposure.

Request an assessment