CVE-2024-45047: Potential mXSS vulnerability due to improper HTML escaping in svelte

Published Aug 30, 2024
·
Updated

Summary

A potential XSS vulnerability exists in Svelte for versions prior to 4.2.19.

Details

Svelte improperly escapes HTML on server-side rendering. It converts strings according to the following rules:

- If the string is an attribute value: - " -> &quot; - & -> &amp; - Other characters -> No conversion - Otherwise: - < -> &lt; - & -> &amp; - Other characters -> No conversion

The assumption is that attributes will always stay as such, but in some situation the final DOM tree rendered on browsers is different from what Svelte expects on server-side rendering. This may be leveraged to perform XSS attacks. More specifically, this can occur when injecting malicious content into an attribute within a <noscript> tag.

PoC

A vulnerable page (+page.svelte): html <script> import { page } from "$app/stores"

// user input let href = $page.url.searchParams.get("href") ?? "https://example.com"; </script>

<noscript> <a href={href}>test</a> </noscript>

If a user accesses the following URL, http://localhost:4173/?href=</noscript><script>alert(123)</script> then, alert(123) will be executed.

Impact

XSS, when using an attribute within a noscript tag

Other sources

svelte performance oriented web framework. A potential mXSS vulnerability exists in Svelte for versions up to but not including 4.2.19. Svelte improperly escapes HTML on server-side rendering. The assumption is that attributes will always stay as such, but in some situation the final DOM tree rendered on browsers is different from what Svelte expects on server-side rendering. This may be leveraged to perform XSS attacks, and a type of the XSS is known as mXSS (mutation XSS). More specifically, this can occur when injecting malicious content into an attribute within a noscript tag. This issue has been addressed in release version 4.2.19. Users are advised to upgrade. There are no known workarounds for this vulnerability.

MITRE

Affected Software

2 affected componentsFixes available
npm/svelte<4.2.19
4.2.19
svelte Svelte Node.js<4.2.19

Event History

Aug 30, 2024
Advisory Published
via GitHub·04:49 PM
CVE Published
via MITRE·04:55 PM
Data Sourced
via MITRE·04:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2024-45047?

CVE-2024-45047 is classified as a moderate severity vulnerability due to its potential for XSS attacks under specific conditions.

2

How do I fix CVE-2024-45047?

To fix CVE-2024-45047, upgrade to Svelte version 4.2.19 or later.

3

Which versions of Svelte are affected by CVE-2024-45047?

CVE-2024-45047 affects all versions of Svelte prior to 4.2.19.

4

What type of vulnerability is CVE-2024-45047?

CVE-2024-45047 is an XSS (Cross-Site Scripting) vulnerability.

5

Is server-side rendering impacted by CVE-2024-45047?

Yes, CVE-2024-45047 arises from improper HTML escaping during server-side rendering in Svelte.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203