php2shell one week later: Why one exploit doesn’t work everywhere
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 expl
- Vendor
- PHP
- Product
- PHP
- CVSS v4.0
- 9.2
- EPSS
- 0.16 (p97)
- Exploitation
- observed in the wild
- Fix
- available
- Exposure class
- Web platform
Why it ranks 79 (Critical)
- Exploitation observed in the wild
- CVSS v4.0 9.2 critical
- EPSS 0.16 (elevated)
- Product class: web platform
- Covered by 38 independent sources
- Fix available
- Threat research
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- Tenable Research (tenable.com)
- CVE-2026-109618 on this site · NVD · CVE.org · Vulnpedia
- CVE-2026-109619 on this site · NVD · CVE.org · Vulnpedia
- CVE-2021-44228 on this site · NVD · CVE.org · Vulnpedia
- CVE-2026-46300 on this site · NVD · CVE.org · Vulnpedia
Related coverage
Other items that share a CVE or were clustered with this one.