Stored XSS via unencoded attachment metadata
Published Feb 5, 2024 · Updated Jun 17, 2025
Stored XSS in phpMyFAQ before 3.2.5 allows remote authenticated users to execute JavaScript in an administrator's browser via an attachment. The admin attachment table in attachments.php directly echoes attacker-controlled filename, language, and MIME-type values without HTML encoding. Attachment-upload permission is required; viewing the attachment list triggers the stored payload, which acts with the viewing administrator's session privileges.
Summary
What happened
Stored XSS in phpMyFAQ before 3.2.5 allows remote authenticated users to execute JavaScript in an administrator's browser via an attachment. The admin attachment table in attachments.php directly echoes attacker-controlled filename, language, and MIME-type values without HTML encoding. Attachment-upload permission is required; viewing the attachment list triggers the stored payload, which acts with the viewing administrator's session privileges.
The record
- CVE
- CVE-2024-24574
- Published
- Feb 5, 2024
- Updated
- Jun 17, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-80, CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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.5
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 attachment-filename stored-XSS 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