Stored XSS via unsanitized comment fields
Published Mar 2, 2023 · Updated Mar 7, 2025
Stored XSS in the comment system of FlatPress before 1.3 allows remote attackers to persist scripts through unsanitized fields. The comment_clean function passed author name, email, URL, and content through filters but retained HTML tags before storing the comment. A submitted comment must be accepted and rendered, causing injected script to execute in a visitor's browser under the blog's origin.
Summary
What happened
Stored XSS in the comment system of FlatPress before 1.3 allows remote attackers to persist scripts through unsanitized fields. The comment_clean function passed author name, email, URL, and content through filters but retained HTML tags before storing the comment. A submitted comment must be accepted and rendered, causing injected script to execute in a visitor's browser under the blog's origin.
The record
- CVE
- CVE-2023-1147
- Published
- Mar 2, 2023
- Updated
- Mar 7, 2025
- Vendor
- FlatPress
- Product
- FlatPress
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 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 <1.3
What conditions does exploitation require?
What is affected?
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 stored-XSS 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