Stored XSS via permitted .xsig uploads
Published Mar 20, 2025 · Updated Mar 20, 2025
Stored cross-site scripting in the FlatPress uploader before 1.3 allows attackers to run JavaScript through a crafted .xsig file. The uploader denylist omits the xsig extension, while direct retrieval serves the uploaded file as application/octet-stream and browsers process its markup. Exploitation requires a user to upload and directly open the file; the script then runs in the same-origin context and can access cookies and content or issue requests.
Summary
What happened
Stored cross-site scripting in the FlatPress uploader before 1.3 allows attackers to run JavaScript through a crafted .xsig file. The uploader denylist omits the xsig extension, while direct retrieval serves the uploaded file as application/octet-stream and browsers process its markup. Exploitation requires a user to upload and directly open the file; the script then runs in the same-origin context and can access cookies and content or issue requests.
The record
- CVE
- CVE-2024-4023
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- FlatPress
- Product
- FlatPress
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 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?
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 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