Stored XSS via unescaped directory listing values
Published May 1, 2024 · Updated Aug 2, 2024
Stored XSS in Static Web Server before 2.30.0 allows remote attackers to execute JavaScript through crafted directory entries. The directory-listing renderer inserts file_name and current_path values into HTML without escaping special characters. Exploitation requires directory listings, attacker-controlled names, and a victim who opens the listing; script runs in the server origin.
Summary
What happened
Stored XSS in Static Web Server before 2.30.0 allows remote attackers to execute JavaScript through crafted directory entries. The directory-listing renderer inserts file_name and current_path values into HTML without escaping special characters. Exploitation requires directory listings, attacker-controlled names, and a victim who opens the listing; script runs in the server origin.
The record
- CVE
- CVE-2024-32966
- Published
- May 1, 2024
- Updated
- Aug 2, 2024
- Vendor
- Static Web Server
- Product
- Static Web Server
- Classifications
- CWE-80, CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=0 <2.30.0
- Affected versionversion=< 2.30.0
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
- Upstream malicious-filename 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