Authenticated script execution via unencoded profile fields
Published Apr 22, 2023 · Updated Feb 4, 2025
Stored XSS in phpMyFAQ before 3.1.12 allows remote authenticated users to execute script in another user's browser through user profile fields. In admin/user.php, display_name and last_modified POST values were accepted with FILTER_UNSAFE_RAW instead of conversion to HTML entities before storage and rendering. An account able to submit those fields is required, and the resulting script runs in the phpMyFAQ origin when the stored values are viewed.
Summary
What happened
Stored XSS in phpMyFAQ before 3.1.12 allows remote authenticated users to execute script in another user's browser through user profile fields. In admin/user.php, display_name and last_modified POST values were accepted with FILTER_UNSAFE_RAW instead of conversion to HTML entities before storage and rendering. An account able to submit those fields is required, and the resulting script runs in the phpMyFAQ origin when the stored values are viewed.
The record
- CVE
- CVE-2023-1875
- Published
- Apr 22, 2023
- Updated
- Feb 4, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2023CVE publishedPublication date reported by the CVE source.
- Feb 4, 2025Record 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.12
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