Script injection via unescaped error messages
Published Nov 25, 2024 · Updated Nov 25, 2024
Cross-site scripting in Svelte SvelteKit before 2.8.3 allows remote authenticated users to inject script through crafted error messages. The static error.html renderer substitutes %sveltekit.error.message% without HTML escaping, placing markup from an explicitly created server error into the response. Exploitation requires application code to put user input in a custom Error message and a user to render that error page; uncaught errors use a fixed internal-error message.
Summary
What happened
Cross-site scripting in Svelte SvelteKit before 2.8.3 allows remote authenticated users to inject script through crafted error messages. The static error.html renderer substitutes %sveltekit.error.message% without HTML escaping, placing markup from an explicitly created server error into the response. Exploitation requires application code to put user input in a custom Error message and a user to render that error page; uncaught errors use a fixed internal-error message.
The record
- CVE
- CVE-2024-53262
- Published
- Nov 25, 2024
- Updated
- Nov 25, 2024
- Vendor
- Svelte
- Product
- SvelteKit
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 25, 2024CVE publishedPublication date reported by the CVE source.
- Nov 25, 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=< 2.8.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
No public exploit references are available in this record.
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