The PHP project has fixed 17 security vulnerabilities in one release. One of them, phpAfterShell, carries a CVSS score of 9.2, the highest severity rating. Cloudflare had already deployed rules that block some known attack indicators by default, but upgrading PHP and restarting its workers remain essential to fully remediate the flaws.
What this is
phpAfterShell is a vulnerability in PHP’s default file session handler. If the process is interrupted while an application writes a session file, the file may contain both old and new data. When it is later read and deserialized, an attacker may be able to inject malicious content and ultimately achieve remote code execution.
The PHP team has released 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0, addressing 16 additional vulnerabilities, six of which are also classified as severe. Cloudflare’s web application firewall (WAF), which filters and blocks malicious web requests, now covers known attack patterns for phpAfterShell. The protection is enabled by default even on the free plan.
Industry view
This release sends a clear signal: security protection is moving from “respond after a vulnerability is disclosed” toward using historical attack indicators to cover unknown variants in advance. Cloudflare says its rules were already identifying some attack paths before the disclosure and were then expanded with new indicators. This capability is particularly valuable for operations teams whose systems update frequently and whose staff cannot manually track every request.
But a firewall is not a complete answer. Some critical vulnerabilities depend on server configuration or can be triggered through paths invisible to the WAF. Cloudflare itself explicitly states that a full fix requires upgrading PHP and restarting every worker process. In addition, three new paid rules only log traffic by default rather than blocking it because the relevant requests may also come from legitimate business activity; blocking them outright could cause service outages. As of November 19, no evidence had emerged that these vulnerabilities had been exploited in the wild. That lowers the immediate risk but does not justify delaying upgrades.
Impact on regular people
For enterprise IT: Teams running PHP should promptly verify their versions, schedule upgrades, restart workers, and review security logs. WAF rules are useful as a buffer before patches are deployed, not as a substitute for them.
For individual professionals: Anyone responsible for website maintenance, e-commerce, or enterprise systems needs to incorporate session mechanisms and dependency updates into routine checklists, rather than focusing only on front-end functionality while overlooking security at the server level.
For the consumer market: There is currently no evidence that the vulnerabilities have been exploited in real-world attacks, so ordinary users do not need to replace their products immediately. However, websites running outdated PHP versions may still be exposed because of poor administration.