Stored XSS via undisclosed input handling
Published Oct 19, 2022 · Updated May 8, 2025
Stored XSS in phpMyFAQ 3.1.7 and earlier allows remote authenticated users to execute script in another user's browser. Published records and the referenced commit do not identify the input field or rendering locus that fails to neutralize stored content. Exploitation requires high-privileged access and a user to view the stored content; script execution can expose or alter browser-accessible data.
Summary
What happened
Stored XSS in phpMyFAQ 3.1.7 and earlier allows remote authenticated users to execute script in another user's browser. Published records and the referenced commit do not identify the input field or rendering locus that fails to neutralize stored content. Exploitation requires high-privileged access and a user to view the stored content; script execution can expose or alter browser-accessible data.
The record
- CVE
- CVE-2022-3608
- Published
- Oct 19, 2022
- Updated
- May 8, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- May 8, 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.2.0-alpha
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
- huntr.dev bounty proof of conceptproof of concept · unverified
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