The crisis began in earnest on October 20, when The PHP Foundation, the organization responsible for maintaining the language, issued a pre-announcement warning of an impending security patch. The foundation had been alerted to the vulnerabilities by independent security researchers and worked feverishly to develop fixes before the details became public knowledge. However, the timeline between discovery and exploitation proved to be razor-thin.
While the official patches were released on Wednesday, October 23, the digital landscape was already under siege. Reports of active exploitation began to surface almost immediately, suggesting that threat actors may have reverse-engineered the vulnerability or discovered it independently through their own research.
The scale of the attack was highlighted by Cloudflare CEO Matthew Prince, who provided real-time data on the surge of malicious activity. In a series of updates on the social media platform X, Prince revealed that Cloudflare’s global network began detecting "thousands of attempts to exploit it" even in the hours before the official public announcement. The situation escalated with startling speed once the news broke.
"Across the Cloudflare network we saw thousands of attempts to exploit it," Prince wrote. "That jumped to tens of thousands in the 45 minutes post-announcement, hundreds of thousands within 2 hours, and millions now."
This rapid escalation illustrates the automated nature of modern cyber warfare. As soon as a vulnerability is disclosed, botnets and automated scanning tools are deployed to scour the internet for vulnerable targets. For an organization running an unpatched PHP server, the question is often not if they will be scanned, but how many seconds it will take for an automated exploit to find them.
CISA Recommendations and Implementation Challenges
In addition to the hard deadline for federal agencies, CISA’s advisory provides a roadmap for broader organizational resilience. The agency emphasized that patching is the only definitive solution, but acknowledged that the path to remediation is rarely simple in complex enterprise environments.
Ramy Rahman, a senior principal solutions engineer at ArmorCode, noted that while the three-day deadline for federal agencies is aggressive, it is achievable for organizations that have invested in modern vulnerability management tools. However, he cautioned that the "dependency hell" often associated with legacy systems remains a formidable barrier.
"The biggest challenge will be the versions of PHP they’re running, and the dependencies tied to them," Rahman explained. "Administrators should prioritize upgrading to the patched versions of PHP, including 8.5.12, 8.4.27, 8.3.36, or 8.2.35, depending on their release branch."
