Svelte version 1.13.1 is a patch release following closely after version 1.13.0, both iterations of the "magical disappearing UI framework." Examining the package data reveals a minimal change set, primarily focusing on bug fixes and minor improvements rather than introducing new features. Both versions share identical dependencies, including core tools like magic-string for string manipulation, and a suite of development dependencies crucial for building, testing, and linting the Svelte compiler. Key development tools span across bundling (rollup), testing (mocha, jsdom, nyc), code analysis (eslint, css-tree), and ES6 transpilation using Babel and associated plugins.
For developers using Svelte, this suggests upgrading from 1.13.0 to 1.13.1 should be a straightforward process with minimal risk of breaking changes. The quick release of the patch version likely addresses immediate concerns that arose from the initial 1.13.0 release, solidifying the stability within the 1.x series. As a framework known for its compile-time approach, minimizing runtime overhead, these incremental improvements contribute to a more refined developer experience, ensuring smooth workflows when crafting performant web applications with Svelte. The common MIT license and Rich Harris as the author assure open-source usability and a singular point of contact for the project's vision.
All the vulnerabilities related to the version 1.13.1 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