Svelte version 2.13.2 is a minor patch release following 2.13.1 in the 2.x series of this "magical disappearing UI framework". Both versions share the same core development dependencies, including tools for testing (mocha, nyc), linting (eslint), bundling (rollup), and TypeScript support. Developers familiar with the Svelte ecosystem will find a consistent development experience across these versions. Key dependencies like rollup-plugin-typescript for seamless TypeScript integration within Svelte components and rollup-plugin-node-resolve for resolving Node.js modules remain the same.
The primary difference between the two versions lies in the dist metadata, specifically the unpackedSize. Version 2.13.2 has an unpacked size of 1015648 bytes, a slight increase from version 2.13.1's 1013662 bytes. This suggests that the patch release likely introduced minor bug fixes or small improvements to the core library. The release date difference indicates it addressed issues relatively soon after the initial 2.13.1 release, ensuring a more stable development experience. For developers, upgrading from 2.13.1 to 2.13.2 is recommended to benefit from these improvements and ensure the use of the most up-to-date stable release within the 2.x series of Svelte. The fileCount remains consistent at 12 for both versions.
All the vulnerabilities related to the version 2.13.2 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