Svelte 1.0.6 is a minor patch release following Svelte 1.0.5 in the early days of the magical disappearing UI framework. While both versions share identical descriptions and core development philosophies centered around shifting work from the browser to the compile step using a JavaScript compiler, a key difference lies in the updated dependency: magic-string. Version 1.0.6 incorporates magic-string at version ^0.19.0, a notable upgrade from the ^0.16.0 version used in 1.0.5.
For developers, this seemingly small change can translate to improved source map accuracy and potentially better debugging experiences. Magic-string plays a crucial role in Svelte's compilation process by providing efficient and accurate manipulation of source code strings, ensuring that mappings between the original source and the compiled output are maintained. The other dependencies are the same between both versions.
While both versions maintain the same suite of development tools, including Rollup, ESLint, and Babel, the updated magic-string dependency in Svelte 1.0.6 suggests a refinement of the underlying compilation mechanics. Furthermore given both package versions are very close in time, developers might want to use the latest one. Svelte is known for being a compiler that writes no javascript and having great performance, a new project might benefit from using it.
All the vulnerabilities related to the version 1.0.6 of the package
Svelte vulnerable to XSS when using objects during server-side rendering
The package svelte before 3.49.0 is vulnerable to Cross-site Scripting (XSS) due to improper input sanitization and to improper escape of attributes when using objects during SSR (Server-Side Rendering). Exploiting this vulnerability is possible via objects with a custom toString() function.
Svelte has a potential mXSS vulnerability due to improper HTML escaping
A potential XSS vulnerability exists in Svelte for versions prior to 4.2.19.
Svelte improperly escapes HTML on server-side rendering. It converts strings according to the following rules:
" -> "& -> &< -> <& -> &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.
A vulnerable page (+page.svelte):
<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.
XSS, when using an attribute within a noscript tag