Svelte version 1.44.0 arrived on December 3rd, 2017, succeeding version 1.43.1, released just days before on November 27th, 2017. Both versions share the core description of Svelte as "The magical disappearing UI framework," highlighting its key feature: compiling away into highly efficient vanilla JavaScript during the build process. A comparison reveals identical listings of devDependencies, encompassing a comprehensive suite of tools necessary for development, testing, and building the Svelte library itself. These include essential packages like rollup for bundling, typescript for type checking, eslint for code linting, and mocha with jsdom for testing. The consistent dependency list suggests that the core focus of the update likely involved internal bug fixes, performance improvements, or minor feature additions, rather than a major overhaul necessitating changes to the development tooling. For developers, this indicates a stable upgrade path. Existing projects built with Svelte 1.43.1 should transition smoothly to 1.44.0, benefiting from any refinements without requiring substantial code modifications. The unchanged devDependencies also reassure developers that their existing build processes and development environments will remain compatible. Svelte's commitment to a seamless developer experience is further emphasized by this smooth transition, allowing developers to concentrate on building their applications rather than wrestling with framework updates.
All the vulnerabilities related to the version 1.44.0 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