FAQ page disruption via unsanitized stored HTML
Published Jan 2, 2025 · Updated Jan 2, 2025
Stored HTML injection in phpMyFAQ 3.2.10 through 4.0.1 allows remote authenticated users to disrupt FAQ pages via crafted entries. The FAQ editor stores user-controlled markup without adequate sanitization or escaping, and the frontend renders malformed elements that can overlap the entire interface. Administrative editing access is required, and another user must view the affected FAQ for the stored content to disrupt, deface, or imitate the page.
Summary
What happened
Stored HTML injection in phpMyFAQ 3.2.10 through 4.0.1 allows remote authenticated users to disrupt FAQ pages via crafted entries. The FAQ editor stores user-controlled markup without adequate sanitization or escaping, and the frontend renders malformed elements that can overlap the entire interface. Administrative editing access is required, and another user must view the affected FAQ for the stored content to disrupt, deface, or imitate the page.
The record
- CVE
- CVE-2024-56199
- Published
- Jan 2, 2025
- Updated
- Jan 2, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-80, CWE-79, T1499.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 2, 2025CVE publishedPublication date reported by the CVE source.
- Jan 2, 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=>= 3.2.10, < 4.0.2
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
- Upstream stored HTML injection proof of conceptproof of concept · demonstrated
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