CVE-2026-129292
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
3Patches
Vulnerability mechanics
References
1News mentions
3- PHP Releases Patches to Fix 18 VulnerabilitiesInfosecurity Magazine · Nov 19, 2026
- PHP’s November 2026 Security Release: What Reaches WordPressPatchstack Blog · Nov 19, 2026
- PHP Warns of Critical Security Flaws Affecting All Supported Versions, Urges Users to UpdateCyber Security News · Nov 19, 2026