Stored XSS via unsanitized FAQ content
Published Dec 16, 2023 · Updated Aug 2, 2024
Stored XSS in phpMyFAQ before 3.1.17 allows remote authenticated users to execute script via crafted FAQ content. FaqHelper and SearchHelper rendered category, FAQ, and search-result fields without converting untrusted HTML to entities, allowing stored payloads to run when pages were viewed. Exploitation requires an account permitted to add or modify FAQ content and a victim to load the affected page; impact is client-side script execution in the victim session.
Summary
What happened
Stored XSS in phpMyFAQ before 3.1.17 allows remote authenticated users to execute script via crafted FAQ content. FaqHelper and SearchHelper rendered category, FAQ, and search-result fields without converting untrusted HTML to entities, allowing stored payloads to run when pages were viewed. Exploitation requires an account permitted to add or modify FAQ content and a victim to load the affected page; impact is client-side script execution in the victim session.
The record
- CVE
- CVE-2023-6890
- Published
- Dec 16, 2023
- Updated
- Aug 2, 2024
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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