Stored XSS via unsanitized upload filename
Published Mar 20, 2025 · Updated Mar 20, 2025
Stored XSS in FlatPress before 1.4.dev allows remote authenticated users to execute JavaScript in another user's browser via a filename. The admin uploader's onupload path accepted the client-supplied upload name and passed its stem through sanitize_title, which did not strip script-bearing filename characters; the patch adds an allowlist-based sanitize_filename operation. An authenticated uploader must plant the filename and another user must access the uploaded file, exposing that user's same-origin data and actions.
Summary
What happened
Stored XSS in FlatPress before 1.4.dev allows remote authenticated users to execute JavaScript in another user's browser via a filename. The admin uploader's onupload path accepted the client-supplied upload name and passed its stem through sanitize_title, which did not strip script-bearing filename characters; the patch adds an allowlist-based sanitize_filename operation. An authenticated uploader must plant the filename and another user must access the uploaded file, exposing that user's same-origin data and actions.
The record
- CVE
- CVE-2024-9699
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- FlatPress
- Product
- FlatPress
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
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.4.dev
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 file-upload filename 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