{"vuln_id":"GHSA-7qg2-v9fj-4mwv","aliases":["CVE-2026-6735"],"description":"XSS within PHP-FPM status endpoint","published_at":"2026-05-07T12:56:51Z","modified_at":"2026-05-07T12:56:51Z","first_seen_at":"2026-11-21T19:15:07.670957Z","severity":"medium","severity_source":"ghsa","cvss_score":7.6,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","cwe":["CWE-79"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":null,"epss_percentile":null,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://github.com/advisories/GHSA-7qg2-v9fj-4mwv"},"matched_alias":null,"items":[{"id":636,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-3mg3-cr28-46gc / CVE-2026-129292: PHP-FPM status endpoint XSS via unescaped user and script fields","summary":"PHP-FPM status endpoint XSS via unescaped user and script fields\n\n### Summary\r\n\r\nPHP-FPM can include attacker-controlled request metadata without escaping it in the full status response. An unauthenticated attacker can place HTML or JavaScript in a worker's scoreboard entry and execute it in the browser of an operator who later views the full HTML status page. The attacker does not need access to the status endpoint.\r\n\r\n### Details\r\n\r\nThe earlier fix for [CVE-2026-6735](https://github.com/php/php-src/security/advisories/GHSA-7qg2-v9fj-4mwv) escaped the request URI and query string, but left the request method, authentication user and script filename unescaped in the per-process status output. These values are stored in the PHP-FPM scoreboard and later inserted into HTML, XML and JSON responses without the encoding required by each format.\r\n\r\nThe most direct attack uses the username from an HTTP Basic authentication header. When the front end forwards this header to PHP-FPM, PHP can decode and store the supplied username even if the application does not use Basic authentication. The scoreboard retains up to 31 bytes of the username, which is enough for an HTML element with a JavaScript event handler. A request to an ordinary PHP script in the pool can therefore plant a payload that runs when another user opens the status endpoint with `full&html`. The value remains in that worker's scoreboard entry until it is replaced by a later request.\r\n\r\nThe script filename provides another injection path when an attacker can influence the filename recorded by FPM, including configurations using `cgi.fix_pathinfo=0`. Ordinary web servers restrict the characters accepted in request methods, so the request-method field does not by itself establish the same HTTP attack path. Unescaped quotes or markup in these fields can also corrupt JSON or XML status responses and interfere with monitoring consumers.\r\n\r\nThe fix applies a common, format-appropriate escaping helper to the request method, request URI, query string, authentication user and script filename before rendering the full status response. A separate client-side injection issue in the bundled `status.html` dashboard is tracked in [GHSA-q8fm-p8fx-h6r6](https://github.com/php/php-src/security/advisories/GHSA-q8fm-p8fx-h6r6).\r\n\r\n### Impact\r\n\r\nExploitation requires an enabled PHP-FPM status endpoint, a request path through which attacker-controlled metadata reaches the affected pool, and a user or tool that renders the full status data as HTML. For the authentication-user attack, the front end must forward the Basic authentication header to FPM. Restricting access to the status endpoint does not prevent an attacker from planting the payload through a separate application request.\r\n\r\nSuccessful exploitation runs JavaScript in the status page's origin. It can expose request URIs, query strings and other information shown on the status page. If the page shares an origin with the application, the script can also act with the viewing user's session and read data available to that \n\nAffected packages: php:sapi-fpm\nPatched: sapi-fpm 8.2.36, sapi-fpm 8.3.37, sapi-fpm 8.4.28, sapi-fpm 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-3mg3-cr28-46gc","published_at":"2026-11-19T14:07:47Z","updated_at":"2026-11-19T18:42:44Z","fetched_at":"2026-11-21T19:15:07.553373Z","severity":"high","cvss_score":7.6,"epss":0.0107,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"sapi-fpm","vuln_id":"CVE-2026-129292","vuln_ids":["CVE-2025-14179","CVE-2026-115560","CVE-2026-12184","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-3MG3-CR28-46GC","GHSA-7QG2-V9FJ-4MWV","GHSA-Q8FM-P8FX-H6R6"],"tags":["repo-advisory","php","CWE-79","security","repo:php/php-src"],"cluster_id":464,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/636","html":"https://vulnwatch.ve1ve2.com/item/636"}},{"id":12642,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-7qg2-v9fj-4mwv / CVE-2026-6735: XSS within PHP-FPM status endpoint","summary":"XSS within PHP-FPM status endpoint Improper sanitization of the request URI within the PHP-FPM status page allows an attacker to execute arbitrary JavaScript code (XSS) on the victims machine, possibly stealing cookies on insufficiently hardened systems, or stealing other sensitive data such as the information from the status page itself. An attacker does not require authentication or access to the `/status` endpoint in order to trigger XSS, but may simply visit a URI embedding the malicious code. 1. Navigate to `example.com/` 2. Navigate to `example.com/status?full&html` 3. Observe the JavaScript pop-up. The same is possible for the XML endpoint, possibly embedding malicious XML nodes into the status report. 1. Navigate to `example.com/<` 2. Navigate to `example.com/status?full&xml` 3. Observe the XML parsing error. Affected packages: php:PHP-FPM Patched: PHP-FPM 8.2.31, PHP-FPM 8.3.31, PHP-FPM 8.4.21, PHP-FPM 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-7qg2-v9fj-4mwv","published_at":"2026-05-07T12:56:51Z","updated_at":"2026-05-07T12:56:51Z","fetched_at":"2026-11-22T14:05:37.431183Z","severity":"high","cvss_score":7.6,"epss":0.00193,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"PHP-FPM","vuln_id":"CVE-2026-6735","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-7QG2-V9FJ-4MWV"],"tags":["repo-advisory","php","CWE-79","security","repo:php/php-src","stack"],"cluster_id":465,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12642","html":"https://vulnwatch.ve1ve2.com/item/12642"}}]}