Severity: HighThe Hacker News

PHP2Shell: Two Unpatched Critical PHP RCE Flaws (CVSS 9.2) Trigger Emergency Security Alert

PHP announced an out-of-cycle security release (14:00 UTC, Oct 21, 2026) for two critical RCE flaws rated CVSS v4.0 9.2, dubbed PHP2Shell by researchers after a leak. Technical details, affected versions and root cause were unpublished, and only PHP 8.2 to 8.5 would receive fixes.

Key takeaways

  1. Two unpatched critical PHP RCE flaws (CVE-2026-109618, CVE-2026-109619) are under embargo; PHP's own rating is CVSS v4.0 9.2, not the leaked 10.0.
  2. Affected-version scope is unconfirmed; only PHP 8.2 to 8.5 will receive vendor fixes, so end-of-life branches (8.1 and older) get no patch.
  3. The CVE IDs come from a leaked post and researcher commentary; PHP's notice names neither, and no workaround or technical detail has been published.
  4. About 884,000 internet-facing hosts advertise PHP 8.1 or older in their banner and are exposed if the flaws reach end-of-life branches.
  5. No exploitation or public PoC was known as of Oct 21, but CVE-2024-4577 drew exploit attempts within 24 hours of disclosure.

Why it matters

PHP runs a large share of internet-facing web applications, and both flaws are reachable over HTTP without authentication.

No exploit signature is possible yet, so coverage comes from what follows code execution: shells from PHP workers, download tools, and scripts written to the web root.

What to do

  • Patch to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 as soon as the release ships.
  • Restart every PHP-FPM pool and Apache worker after patching; running workers keep the old code in memory.
  • Hunt for post-exploitation behavior back to at least October 17, not the disclosure date.

Affected technology

  • PHP 8.2 to 8.5
  • PHP-FPM
  • Apache mod_php
  • php-cgi

Detector templates

The detectors drafted from this report.

Each one targets what an attacker has to do, not one indicator. Reveal the logic, or build it for your platform.

  • Severity: High

    Web server or PHP process spawning shell or interpreter

    Detects PHP runtime and web server processes (php-fpm, php-cgi, httpd, apache2 and Windows web hosts) launching command shells, scripting interpreters or similar child processes.

    • T1059Command and Scripting Interpreter
    • T1190Exploit Public-Facing Application
    Why it matters
    A PHP worker has almost no reason to start a shell. When it happens, someone is usually running commands through it.
    How to investigate
    Read the child command line first, then check what the same worker downloaded or wrote in the minutes around it.
    Detection logic4 stepsLocked

    The logic is ready. Leave your details to reveal it.

    Build it for your stackWorks with Microsoft Defender, CrowdStrike Falcon, Cortex XDR, SentinelOne
  • Severity: High

    Download or staging tool launched by PHP web process

    Detects PHP or web server processes starting download or transfer tools (curl, wget, certutil, bitsadmin, PowerShell download cradles) to retrieve second-stage payloads.

    • T1105Ingress Tool Transfer
    Why it matters
    Pulling a second stage is the usual next move after code execution on a web server.
    How to investigate
    Check the destination the tool contacted and whether a new file appeared in a temp or web-accessible directory.
    Detection logic4 stepsLocked

    The logic is ready. Leave your details to reveal it.

    Build it for your stackWorks with Microsoft Defender, CrowdStrike Falcon, Cortex XDR, SentinelOne
  • Severity: Medium

    New script file written to web root by PHP or web server process

    Detects creation or modification of executable script files (.php, .phtml, .phar, .jsp, .aspx) in web-accessible directories by web server or PHP processes, indicating possible web shell deployment.

    • T1505.003Server Software Component: Web Shell
    Why it matters
    A script dropped into the web root gives an attacker a way back in that survives the patch.
    How to investigate
    Open the new file, check who requested it afterwards in the access log, and compare its timestamp with your last deploy.
    Detection logic4 stepsLocked

    The logic is ready. Leave your details to reveal it.

    Build it for your stackWorks with Microsoft Defender, CrowdStrike Falcon, Cortex XDR, SentinelOne
All threat reports

Get started

Run these detectors on your own data.

Port0 replays each detector on your history, tunes it and ships it versioned.