PHP Addresses Two Critical Vulnerabilities: Emergency Updates to Counter Remote Execution Risks
The PHP programming language development team has announced the release of emergency security updates to address two vulnerabilities classified as "critical," receiving a severity rating of 9.2 out of 10. These vulnerabilities allow attackers to execute malicious code remotely without the need for authentication, granting them the ability to take full control of affected servers.
Details of the Vulnerabilities and Affected Versions
These vulnerabilities specifically affect servers using mod_php configurations within Apache servers. The updates addressing these risks include the following PHP versions: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. The development team urges all system administrators to update their servers immediately.
It was also noted that PHP versions 8.1 and earlier no longer receive official support, leaving their users exposed to risks; therefore, it is recommended to migrate to supported versions or obtain security patches from software providers.
The Role of Artificial Intelligence in Discovery
Wiz Research, a company specializing in cybersecurity, revealed that the discovery of these complex vulnerabilities in the PHP source code was assisted by advanced artificial intelligence models, specifically Gemini 4 Argon and GPT-5.6 Sol. The Gemini 4 Argon model played a pivotal role in analyzing the code and verifying the security patches, highlighting the importance of artificial intelligence in enhancing the security of open-source software infrastructure.
Why Was the Remediation Delayed?
The PHP development team acknowledged a "structural failure" that led to a delay in addressing one of the vulnerabilities, the first indicators of which were observed in 2024. The team explained that a lack of resources and technical disputes hindered the solution at that time. However, security reviews conducted as part of OpenAI's "Patch the Planet" program last August and September contributed to providing concrete evidence on how the vulnerability could be exploited, which prompted the team to accelerate the pace of the fix following the leak of information regarding the vulnerabilities on social media.