vulnerability
Imported story
PHP2Shell aftershock: 18 more PHP flaws put enterprise web admins on alert
Source: CSO Online · Published · Last checked 1 hour ago · 3 min read

Publisher excerpt From CSO Online
PHP continues to root out flaws in its architecture, this week releasing fixes for a slew of additional security issues in the wake of PHP2Shell. The patches address 18 vulnerabilities, including a critical request smuggling flaw that could allow unauthenticated attackers to remotely execute code on vulnerable servers. Other vulnerabilities affect PHP’s core engine, session handling, process manager, and Common Gateway Interface (CGI) protocol, which bridges web servers with external application programs. The updates were released for all supported PHP versions, with PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36 containing the fixes. The disclosure comes as enterprises continue to grapple with the full impact of PHP2Shell, a pair of 9.2-severity-rated vulnerabilities disclosed in October. The flaws prompted the outright shutdown of some government websites, and, by some estimates, have borne the brunt of millions of exploit attempts. “Enterprises should read this release as PHP2Shell’s aftershock: Smaller, but it shakes the same walls,” said Frank Dickson of Dickson Research. Flaws enabling RCE, DoS, memory corruption One of the most serious flaws disclosed this week, CVE-2026-129289, is rated a critical 9.2 on the Common Vulnerabilities Scoring System (CVSS). The request smuggling vulnerability impacts PHP-FPM, a background service that executes code for high-volume websites and apps. If exploited, the flaw could allow unauthenticated actors to execute PHP code remotely on vulnerable servers that reuse connections to PHP-FPM under certain conditions. It impacts specific nginx, Apache, HAProxy, and LSAPI configurations that reuse backend connections to PHP-FPM. When paired with a code execution bug, it can “carry an attacker from the web worker toward the whole server,” Dickson explained. Several of the other patches also address vulnerabilities that could allow remote code execution (RCE). Still others address issues including information disclosure, memory corruption, denial-of-service (DoS) interruptions, potentially unsafe handling of HTTPS and FTPS URLs, and cross-site scripting. While there may be heavy focus on the 9.2-rated CVE-2026-129289, the lesser flaws still matter, Dickson said. For instance, in one case, one capital letter turned off encryption; a URL written as HTTPS:// or FTPS:// with an uppercase S could send passwords, tokens, form data, and files in plaintext, even through a redirect, to anyone watching the network. Not quite PHP2Shell level, but still high priority An attacker who exploits a PHP code-execution flaw gains access to whatever the PHP worker can touch, “which is just about everything,” Dickson said. Successful exploitation executes code with the privileges of the PHP worker, which holds the database password, API keys, cloud credentials, and session data. For example, he described what he called an “ugly” attack path: The threat actor gets in through the web application. Reads the configuration file; Du…
Excerpt only, shown with attribution. This content belongs to the original publisher and has not been independently verified by CyberSecurity.pk.
Related CVEs
Keywords: vulnerabilityrceremote code executionexploitedbackdoorawsthreat actorCVE-2026-129289vulnerability newsCSO Onlinecybersecurity newssecurity news Pakistan
Reference: CSO Online — www.csoonline.com ↗

