thorsten/phpmyfaq
Affected
- introduced
4.0.14, fixed4.0.16(ecosystem)
Fixed versions
4.0.16
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-68951
phpMyFAQ has Stored XSS in user list via admin-managed display_name
Summary
A stored cross-site scripting (XSS) vulnerability allows an attacker to execute arbitrary JavaScript in an administrator’s browser by registering a user whose display name contains HTML entities (e.g., <img ...>). When an administrator views the admin user list, the payload is decoded server-side and rendered without escaping, resulting in script execution in the admin context.
Details
Root cause is the following chain:
display_name (real name) is stored in DB (often as HTML entities, e.g., <img ...>).phpmyfaq/src/phpMyFAQ/User/UserData.php decodes display_name using html_entity_decode(...) (“for backward compatibility”).|raw:phpmyfaq/assets/templates/admin/user/users.twig (users table uses {{ user.display_name|raw }})As a result, an entity-encoded payload becomes active HTML/JS when rendered in the admin user list.
Note: This report is about the display_name field + entity-decoding path. It is distinct from previously published issues focused on the email field.
PoC (minimal reproduction)
Preconditions / configuration
security.enableRegistration = true).Steps
<img src=x onerror=alert(1)>http://127.0.0.1:8080/admin/user/listalert(1) triggers) and the payload is rendered as an actual <img> element.Impact
Stored XSS in the admin context can enable:
Evidence (what I observed)
<img src=x onerror=alert(1)><img src="x" onerror="alert(1)">Affected versions
Confirmed by code inspection
html_entity_decode for display_name in UserData.php and {{ user.display_name|raw }} in users.twig.Confirmed by live reproduction
Environment (tested)
Contact / Credit
Medium Basis: The source's own band: MODERATE
4.0.14, fixed 4.0.16 (ecosystem)4.0.16
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0