Stored XSS via unescaped display name
Published Sep 30, 2023 · Updated Sep 23, 2024
Stored XSS in phpMyFAQ before 3.1.18 allows remote authenticated users to execute script in an administrator's browser via a display name. The get_user_data action in admin/ajax.user.php returns the stored display_name field without converting HTML metacharacters, while the fix applies Strings::htmlentities(). A low-privileged account and an administrator viewing the affected record are required; script execution is confined to the viewer's browser context.
Summary
What happened
Stored XSS in phpMyFAQ before 3.1.18 allows remote authenticated users to execute script in an administrator's browser via a display name. The get_user_data action in admin/ajax.user.php returns the stored display_name field without converting HTML metacharacters, while the fix applies Strings::htmlentities(). A low-privileged account and an administrator viewing the affected record are required; script execution is confined to the viewer's browser context.
The record
- CVE
- CVE-2023-5319
- Published
- Sep 30, 2023
- Updated
- Sep 23, 2024
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 30, 2023CVE publishedPublication date reported by the CVE source.
- Sep 23, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.1.18
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo