SecurityNovember 13, 20267 min read

PHP2Shell: What Testers Should Check Across Every PHP Host

Two critical bugs in the PHP engine itself put every PHP site that serves web requests in scope at once. Exploit attempts started before the patch, and the hard part for most teams is finding every PHP install they run.

What happened

On October 21, the PHP project released PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 to fix CVE-2026-109618 and CVE-2026-109619, two critical engine bugs (CVSS 9.2 each) that can allow unauthenticated remote code execution. The researchers who found them in August were Wiz, OpenAI, and Calif. The PHP team said every installation that serves web requests is at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed, and it considers mod_php the highest risk setup. (CERT-EU, SecurityWeek)

Amazon Threat Intelligence saw an exploitation attempt against its honeypots on October 17, four days before disclosure, and more attempts from varied anonymized infrastructure once proofs of concept appeared. (AWS)

As of October 23, security vendors report broad scanning and failed exploit attempts, including attempts to deliver a Mirai variant called Potassium. No successful in-the-wild compromise has been confirmed. Sophos corrected an earlier report of a successful exploitation. Several organizations still took sites offline as a precaution, and the UK government said 32 of its services were unavailable and four partly unavailable, mostly due to precautionary measures while patches were applied. CISA had not added either CVE to the KEV catalog as of the morning of October 23. (SecurityWeek, Sophos)

Why it matters

Both bugs sit in code nearly every request touches. CERT-EU describes CVE-2026-109618 as memory corruption during out-of-memory handling and CVE-2026-109619 as stale global state that a later request on the same worker can reuse. A demonstrated exploit triggers before any application code runs, so clean application code offers no protection.

Exploitation is harder than the first headlines suggested. Sansec said attackers need detailed knowledge of a server and particular conditions on it, and that public exploits fail against PHP installations with default settings. VulnCheck reported a private exploit that works on production style configurations with ASLR enabled, and expects attackers to catch up. The safe assumption is that reliable public exploits are a matter of time.

The exposure is enormous. Google says vulnerable versions run from PHP 5.4 through 8.5.11 and that the PHP project is not releasing fixes for 8.1 or earlier. Qualys, looking at data from 12,000 customers, found roughly 71% of PHP instances run versions 5.4 through 8.1, which are past end of life. (Google Cloud)

What a tester should check

PHP hides in more places than a web team remembers. The work this week is inventory and verification:

  • Find every PHP host. Web servers, admin panels, vendor appliances, intranet apps, container images, and the forgotten WordPress site on a marketing subdomain all count.
  • Verify the exact version. Confirm each one runs 8.5.12, 8.4.27, 8.3.36, 8.2.35, or later. Banner headers are often hidden or wrong, so record evidence from the package or the host when you have access.
  • Flag end of life branches. Anything on 8.1 or older needs an upgrade plan, and that belongs in the report as its own finding.
  • Check container rebuilds. Google notes that Cloud Run, GKE, and custom images must be rebuilt and redeployed with a patched PHP. A patched base image does nothing until the service is redeployed.
  • Review the interim controls. If a client cannot patch yet, AWS suggests considering blocks on multipart uploads after testing the impact, and hunting web logs for POST requests containing PHP_SESSION_UPLOAD_PROGRESS. Confirm those controls and log reviews exist.

How Zypheron helps a human tester move faster

A bug in a language runtime turns into an inventory problem overnight. In Zypheron, the operator runs service and web fingerprinting across scope, reviews what comes back, and builds a list of every PHP endpoint with its version evidence in one workspace. Each command waits for the operator to approve it.

AI drafts the finding for each host and flags when a recorded build is older than the fixed release, so end of life and unpatched hosts stand out fast. The tester confirms each one before it lands in the report. The client gets a clear list: which hosts are patched, which are not, which are past end of life, with evidence for each.

No tool can promise a client they were never targeted. Zypheron helps a small team answer the question every client is asking this week, where do we run PHP and is it fixed, in hours instead of days.

Try it on your next engagement

Start a 14-day free trial of the Zypheron IDE. No card required, and the Operator plan is $99.99 when you keep going.

Sources

ShareLinkedInX
Email List

Get AD security drops in your inbox

Release notes, identity attack-path research, and early access. Low volume, real signal only. Unsubscribe anytime.

ZYPHERON

ZYPHERON Desktop is a cybersecurity IDE for offensive and defensive workflows. The open source CLI remains available for terminal-first users.

AUTHORIZED USE ONLY

Solutions

Infrastructure

Network

© 2025 ZYPHERON SYSTEMS//DESKTOP + CLI