PHP cross-site scripting in FPM full status page
- Exploited
- No known exploitation
- Fix
- Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13
- Who is exposed
- Not reported
Summary
PHP from PHP Group has a cross-site scripting flaw in its PHP-FPM full status page, which shows the request method, authentication user and script filename without escaping them. A remote attacker without logging in can store JavaScript in a worker's status entry with an ordinary request, such as through a crafted HTTP Basic authentication username, and it runs in the browser of a user who views the full status page as HTML.
Written by a model
Original 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.
What to do
Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129292 (PHP-FPM status endpoint XSS via unescaped user and script fields), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129292 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: fixed in 8.2.36; from 8.3.0, fixed in 8.3.37; from 8.4.0, fixed in 8.4.28; from 8.5.0, fixed in 8.5.13
Fixed versions: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129292 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129292 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-3mg3-cr28-46gc
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129292
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129292"}.Affected versions
- PHP Group PHPfixed in 8.2.36; From 8.3.0 · fixed in 8.3.37; From 8.4.0 · fixed in 8.4.28; From 8.5.0 · fixed in 8.5.13
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/php-src · Advisory GHSA-3mg3-cr28-46gc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129292 |
| Record | NVD · CVE-2026-129292 |
Questions about CVE-2026-129292
Is CVE-2026-129292 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-129292?
PHP: before 8.2.36; from 8.3.0 before 8.3.37; from 8.4.0 before 8.4.28; from 8.5.0 before 8.5.13.
Source: cve.now feed data
How do I fix CVE-2026-129292?
Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Source: cve.now feed data
Related
- CVE-2026-129289PHP-FPM request smuggling through an unread HTTP request body
- CVE-2026-129496Timezone cache use-after-free can lead to remote code execution
- CVE-2026-129481Use-after-free after interrupted session shutdown
- CVE-2026-126714Partially overwritten session files can lead to remote code execution
- CVE-2026-129474Use-after-free in magic method backtraces can lead to remote code execution
- CVE-2026-115560Session serializer mismatch can lead to remote code execution
No corrections so far. Something wrong on this page? Report an error.