Browser script execution via unescaped directory filenames
Published Jan 25, 2023 · Updated Apr 1, 2025
Stored XSS in serve-lite before 1.1.2 allows attackers to execute script in a visitor's browser through a crafted filename. The directory-listing loop interpolates each raw filename into an anchor's URL and text without URI encoding or HTML escaping. Exploitation requires a crafted file in the served directory and a user to open its listing, enabling script execution in that site's origin.
Summary
What happened
Stored XSS in serve-lite before 1.1.2 allows attackers to execute script in a visitor's browser through a crafted filename. The directory-listing loop interpolates each raw filename into an anchor's URL and text without URI encoding or HTML escaping. Exploitation requires a crafted file in the served directory and a user to open its listing, enabling script execution in that site's origin.
The record
- CVE
- CVE-2022-25847
- Published
- Jan 25, 2023
- Updated
- Apr 1, 2025
- Vendor
- Beeno Tung
- Product
- serve-lite
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2023CVE publishedPublication date reported by the CVE source.
- Apr 1, 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=0 <*
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
- XSS in serve-lite 1.1.0 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