PHP patches 18 vulnerabilities, seven marked critical
The November 19 releases fix flaws that PHP says need non-default or uncommon setups, including session-handling remote code execution.
Stored XSS in PHP-FPM status output via unescaped fields
PHP-FPM full status output includes each worker’s request method, authentication user, and script filename without escaping them for HTML, XML, or JSON. With the status endpoint enabled, an unauthenticated remote attacker can store markup in a scoreboard entry using an ordinary request, such as an HTTP Basic username the web server forwards or an attacker-influenced script filename. Viewing the full status page as HTML runs that script in the page’s origin. The attacker need not reach the status endpoint. Bad XML or JSON can also break monitoring tools. PHP 8.2 through 8.5 before the listed fixes are affected.
What to do: Upgrade PHP to 8.2.36, 8.3.37, 8.4.28, or 8.5.13 for the branch in use.
| Product | Affected | Fixed in |
|---|---|---|
| PHP | 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28, 8.5.* before 8.5.13 | 8.2.36, 8.3.37, 8.4.28, 8.5.13 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
PHP-FPM status endpoint XSS via unescaped user and script fields. The PHP-FPM full status output includes the request method, authentication user and script filename of each worker without escaping them for the HTML, XML or JSON format. When the status endpoint is enabled, an unauthenticated remote attacker can store markup in a worker's scoreboard entry with an ordinary request, for example through the username of an HTTP Basic authentication header that the web server forwards to PHP-FPM, or through the script filename where the attacker can influence it. When a user views the full status page as HTML, the injected JavaScript runs in the origin of that page. The attacker does not need access to the status endpoint. Malformed XML or JSON output can also disrupt monitoring tools. This issue affects PHP versions before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
The November 19 releases fix flaws that PHP says need non-default or uncommon setups, including session-handling remote code execution.
Fixed releases are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36; two issues can reach ordinary WordPress hosts.
Today 915 readers · 1K views · 86 reads · all time 211K views