# php2shell one week later: Why one exploit doesn't work everywhere

DevFeed: [php2shell one week later: Why one exploit doesn't work everywhere](<https://devfeed.tech/articles/php2shell-one-week-later-why-one-exploit-doesn-t-work-everywhere-107160.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/php2shell-one-week-later-why-one-exploit-doesnt-work-everywhere>)

Author: Joshua Martinelle, Thomas Cappetta

Published: 2026-10-30T01:42:06Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [CVE-2021-44228](<https://devfeed.tech/topics/cve-2021-44228.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>)

Tags: [appliances](<https://devfeed.tech/tags/appliances.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exploits](<https://devfeed.tech/tags/exploits.md>), [honeypots](<https://devfeed.tech/tags/honeypots.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [internet](<https://devfeed.tech/tags/internet.md>), [memory-handling](<https://devfeed.tech/tags/memory-handling.md>), [network-appliances](<https://devfeed.tech/tags/network-appliances.md>), [online](<https://devfeed.tech/tags/online.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [patch](<https://devfeed.tech/tags/patch.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [scanning](<https://devfeed.tech/tags/scanning.md>)

## AI overview

Tenable's week of testing found that php2shell can enable remote code execution, but exploitation generally requires tuning to the target's PHP build, SAPI, extensions, and runtime configuration. Five exposed vulnerable sites saw exploitation attempts but no compromise; successful execution was reported on researcher honeypots and network appliances. Public probes can misclassify systems: version matches do not prove exploitability, and stateful checks may miss vulnerable hosts or flag patched ones. Checks also depend on memory limits and worker reuse, and can crash workers. Shared-build appliances are a key exception because one tuned exploit may reach many devices. Prioritize patching or isolating internet-facing management interfaces, network appliances, and end-of-life PHP systems; use vendor fixes for appliances. Update PHP to fixed releases or distribution packages, and apply mitigations while upgrading legacy branches.

## Source excerpt

php2shell raised fears of mass exploitation. A week of testing by our research team found that working exploits had to be fitted to each target's exact PHP setup. Systems that share one build, such as network appliances, are the exception: one tuned exploit can reach every device that runs it. Key takeaways The five vulnerable PHP sites we exposed to the internet were not compromised, and public proofs-of-concept (PoCs) that go beyond version checks do not reliably confirm whether a host is vulnerable. Exploitation has been confirmed elsewhere, on researcher honeypots and on some network appliances. In realistic environments, turning php2shell into remote code execution usually takes an exploit built for the specific target. That is hard, not impossible, and it puts php2shell in a different category from Log4Shell, even though both received near-maximum severity ratings. Where many systems share one build, such as network appliances, a single calibrated exploit can work against all of them. Patch now, starting with internet-facing management interfaces, network appliances, and end-of-life PHP branches. Tenable Nessus and Tenable One Web App Scanning have had version-based detection since October 21. Background On October 20, 2026, PHP announced two vulnerabilities, and on October 21 released fixes for flaws that can allow unauthenticated remote code execution. CVE-2026-109618 is an out-of-memory handling flaw. CVE-2026-109619 is a use-after-free flaw caused by stale state shared between requests on the same worker. Each has a CVSSv4 score of 9.2. For a full breakdown of affected versions, fixes and mitigations, see our frequently asked questions blog post. This post covers what happened after the disclosure, based on what our team observed directly. From disclosure to headline in under 48 hours php2shell got big fast. Details of the vulnerabilities leaked online before the official release. Within two days, the vulnerability had a name, a logo and coverage in mainst