Svelte version 1.13.0 arrived on March 26, 2017, building upon the foundation of its predecessor, version 1.12.1, released on March 18, 2017. Both versions share the same core description: "The magical disappearing UI framework," highlighting Svelte's key feature of compiling away into highly efficient vanilla JavaScript during the build process, leading to smaller bundle sizes and improved runtime performance for web applications.
A notable aspect shared by both versions is the dependency on magic-string at version ^0.19.0. This suggests that the core string manipulation and source code transformation capabilities within Svelte remained consistent between these releases. The array of devDependencies is extensive and identical, suggesting that the tooling and testing infrastructure surrounding the Svelte compiler were largely unchanged. This includes tools like rollup for bundling, eslint for code linting, mocha for testing, and a suite of Babel plugins for transpiling JavaScript.
Essentially, upgrading from 1.12.1 to 1.13.0 likely delivered bug fixes, performance improvements, or minor feature enhancements without introducing breaking changes, given the identical dependency and devDependency lists. Developers updating between these versions could anticipate a smooth transition and continued stability in their Svelte projects. These minor version bumps are important for a reliable and optimized work with the library.
All the vulnerabilities related to the version 1.13.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