CRITICALVulnerability
Global
PHP2Shell aftershock: 18 more PHP flaws put enterprise web admins on alert
·Source: CSO Online
Updated:
Executive Summary
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 mana
Analysis
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; Dumps the customer database; Plants a web shell to come back later. He pointed out that PHP warned that PHP2Shell puts every installation serving web requests at risk, with no login required. “This release returns to the same neighborhood: session upload progress, fatal error backtraces, and how PHP behaves when it runs out of memory,” he said. Fritz Jean-Louis , principal cybersecurity advisor at Infotech, agreed that this is a high-priority patching event, if not a PHP2Shell-level emergency. Although several of the critical vulnerabilities require specific configurations or uncommon deployment scenarios, “they still affect one of the most widely deployed web runtimes in the world,” he noted. RCE is the most concerning outcome, as it can give an attacker control over the application server. From there, they may be able to access sensitive business data, steal credentials or session tokens, deploy persistent backdoors, modify application behavior, or use the compromised system as a foothold for deeper intrusion. “Even vulnerabilities that appear less severe, such as information disclosure or memory corruption, can become highly impactful when chained together by a determined attacker,” Jean-Louis said. What enterprises should do now Dickson emphasized the a PHP version number alone will not tell security teams whether they are exposed. Checking the version number is the easy part, but Linux distributions often backport fixes without changing the version string, so the package changelog tells more than the version number does. The hard part is finding every copy: Web servers, containers, hosting control panels, and appliances can all quietly bundle PHP, Dickson said. Then check the settings that matter: Is session upload progress on? Do PHP 8.5 workers include arguments in error backtraces? Does php-cgi face the internet? Is the PHP-FPM status page reachable from outside? He advised security teams to start with internet-facing PHP 8.5 servers, anything with session upload progress enabled, and any setup where several applications share one session store. PHP 8.5 should be first because it is the only branch exposed to the new backtrace flaw, and fatal error backtraces are on by default there, he explained. “Then patch everything else on a normal fast cycle,” Dickson said. He pointed out that PHP 8.2 has just six weeks to live; it will receive no security fixes after December 31, 2026. That means this release may be one of the last it receives. Running 8.2 into January is a risk decision; PHP 8.1 and older, meanwhile, receive no fixes from the PHP project. Interestingly, PHP’s advisory for the new PHP 8.5 backtrace flaw says a change in 8.5.12, the PHP2Shell release, is what made the new attack path reachable. “Emergency fixes are built fast, and fast work sometimes creates a new vulnerability ,” Dickson noted. In light of this, his advice is to preserve the PHP inventory built for PHP2Shell, “and keep it current,” because no one ever said during an incident, “We knew about too many of our PHP servers.” Understanding everywhere PHP runs Jean-Louis agreed that security teams should immediately inventory all PHP deployments, including those embedded in vendor products and appliances. They should also prioritize internet-facing systems, verify PHP-FPM and session management configurations, and deploy the latest supported PHP versions “as quickly as operationally feasible.” Organizations should view this as a continuation of the lesson learned from PHP2Shell, he said: Runtime vulnerabilities deserve the same attention as application vulnerabilities. While PHP2Shell was more “immediately exploitable” and quickly attracted real-world attacks, this release reinforces the need for strong asset inventory, rapid patch deployment, and visibility into underlying software components. “The biggest question for CISOs is not whether they run PHP; it’s whether they know everywhere it runs,” Jean-Louis said.