Stored XSS via unencoded FAQ fields
Published Aug 26, 2025 · Updated Aug 27, 2025
Stored XSS in SourceCodester FAQ Management System 1.0 allows remote authenticated users to execute JavaScript in other users' browsers. The update-faq.php endpoint writes question and answer POST values to tbl_faq without sanitization, and the interface later renders the stored values without output encoding. An attacker needs access to update an FAQ, and execution occurs when another user loads the affected page, enabling browser-context data access or page manipulation.
Summary
What happened
Stored XSS in SourceCodester FAQ Management System 1.0 allows remote authenticated users to execute JavaScript in other users' browsers. The update-faq.php endpoint writes question and answer POST values to tbl_faq without sanitization, and the interface later renders the stored values without output encoding. An attacker needs access to update an FAQ, and execution occurs when another user loads the affected page, enabling browser-context data access or page manipulation.
The record
- CVE
- CVE-2025-57425
- Published
- Aug 26, 2025
- Updated
- Aug 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Stored XSS HTTP request 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