Stored HTML injection via unencoded contentLink
Published Mar 25, 2024 · Updated Aug 2, 2024
Stored HTML injection in phpMyFAQ 3.2.5 allows remote attackers to alter FAQ pages through a crafted contentLink value. The guest FAQ path in phpmyfaq/api.service.php stores contentLink without HTML entity encoding, so supplied markup is rendered when the FAQ is viewed. Exploitation requires guest FAQ creation, administrator approval without detection, and another user's page view; demonstrated effects include content manipulation and redirection.
Summary
What happened
Stored HTML injection in phpMyFAQ 3.2.5 allows remote attackers to alter FAQ pages through a crafted contentLink value. The guest FAQ path in phpmyfaq/api.service.php stores contentLink without HTML entity encoding, so supplied markup is rendered when the FAQ is viewed. Exploitation requires guest FAQ creation, administrator approval without detection, and another user's page view; demonstrated effects include content manipulation and redirection.
The record
- CVE
- CVE-2024-28108
- Published
- Mar 25, 2024
- Updated
- Aug 2, 2024
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-80, CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2024CVE 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=3.2.5
- Affected versionversion=3.2.5 <3.2.6
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
- GitHub Security Advisory contentLink 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