CVE-2026-129292

Cross-Site Scripting
Affects
PHP
in
PHP
No items found.
Versions
<8.2.36, >=8.3.0 <8.3.37, >=8.4.0 <8.4.28, >=8.5.0 <8.5.13

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

PHP is a general-purpose scripting language used mostly for web development. It runs behind web servers through server APIs such as Apache mod_php and PHP-FPM, and powers content management systems and frameworks such as WordPress, Drupal, Moodle and Laravel. PHP-FPM can expose a status endpoint through pm.status_path. Its full output lists, for each worker process, details of the last request, including the request method, request URI, authenticated user and script filename.

A Cross-Site Scripting (XSS) vulnerability (CVE-2026-129292) has been identified in the full status output of PHP-FPM, which allows an unauthenticated attacker to place HTML or JavaScript in a worker's scoreboard entry through ordinary request metadata, and have it run in the browser of an operator who later views the full HTML status page. The attacker does not need access to the status endpoint. The PHP project tracks this issue as GHSA-3mg3-cr28-46gc.

Per MITRE CWE-79: The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

This issue affects all versions of PHP before 8.2.36, PHP 8.3 before 8.3.37, PHP 8.4 before 8.4.28 and PHP 8.5 before 8.5.13, which includes the End-of-Life release lines PHP 5.6, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0 and 8.1 through their final releases.

Details

Module Info

Vulnerability Info

This Medium-severity vulnerability is found in PHP-FPM in all versions of PHP before 8.2.36, PHP 8.3 before 8.3.37, PHP 8.4 before 8.4.28 and PHP 8.5 before 8.5.13, which includes the End-of-Life release lines PHP 5.6, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0 and 8.1 through their final releases. The PHP project scores it 5.3 under CVSS 4.0 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N).

The earlier fix for CVE-2026-6735 escaped the request URI and query string. The request method, authentication user and script filename were still printed as stored in the scoreboard, in the HTML, XML and JSON formats alike. In PHP 8.5.12, the arguments for each process row read:

proc->request_method[0] != '\0' ? proc->request_method : "-",request_uri_string ? request_uri_string : "-",query_string ? "?" : "",query_string ? query_string : "",proc->content_length,proc->auth_user[0] != '\0' ? proc->auth_user : "-",proc->script_filename[0] != '\0' ? proc->script_filename : "-", 

The most direct path is the username from an HTTP Basic authentication header. When the front end forwards the header to PHP-FPM, PHP can decode and store the supplied username even if the application does not use Basic authentication. The scoreboard keeps up to 31 bytes of it, which the advisory notes is enough for an HTML element with a script event handler. The value stays in that worker's scoreboard entry until a later request replaces it.

The script filename is a second path when an attacker can influence the filename that FPM records, including configurations that use cgi.fix_pathinfo=0. Web servers normally restrict the characters allowed in request methods, so that field alone does not provide the same path.

A successful attack runs script in the origin of the status page. It can read the request URIs, query strings and other data shown there, and if the status page shares an origin with the application it can act with the viewing user's session. Unescaped quotes or markup in these fields can also break the JSON and XML status formats and disrupt monitoring tools.

Exploitation requires an enabled status endpoint, a request path through which attacker-controlled metadata reaches the pool, and a person or tool that renders the full status data as HTML. Restricting access to the status endpoint does not stop an attacker from planting the value through a normal application request. The same unescaped fields are present in the final releases of the End-of-Life PHP 5.6 through 8.1 lines.

The fix passes all five fields through a common helper that applies the escaping each output format needs:

request_method_string ? request_method_string : "-",request_uri_string ? request_uri_string : "-",query_string ? "?" : "",query_string ? query_string : "",proc->content_length,auth_user_string ? auth_user_string : "-",script_filename_string ? script_filename_string : "-", 

Mitigation

The PHP project publishes security fixes only for its supported release lines. PHP 5.6, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0 and 8.1 are End-of-Life and will not receive any public updates to address this issue.

Until an upgrade is possible, disable the PHP-FPM status endpoint or avoid its full HTML output. If full status data is required, use a consumer that validates the response and treats every field value as untrusted text.

Users of the affected components should apply one of the following mitigations:

  • Upgrade to PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, or later.
  • Leverage a commercial support partner like HeroDevs (NES for PHP) for post-EOL security support.

Credits

Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Medium
ID
CVE-2026-129292
PROJECT Affected
PHP
Versions Affected
<8.2.36, >=8.3.0 <8.3.37, >=8.4.0 <8.4.28, >=8.5.0 <8.5.13
NES Versions Affected
Published date
November 19, 2026
≈ Fix date
November 19, 2026
Fixed in
Category
Cross-Site Scripting
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
PHP
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.