Svelte 3.2.0 is a minor release over Svelte 3.1.0, both aiming to provide developers with a "cybernetically enhanced" approach to building web applications. The core description and licensing remain consistent between the versions, indicating a stable project with an MIT license suitable for various uses. Both versions share the same core development dependencies, suggesting a unified development process. Key tools like Rollup, TypeScript, and ESLint are used to build, type-check, and lint the Svelte codebase, ensuring a robust and maintainable library.
The most noticeable difference lies in the dist section. Svelte 3.2.0 has a slightly larger unpacked size - 1005321 bytes vs 1001397 bytes from version 3.1.0 and a newer release date, indicating bug fixes, performance improvements, or new features. While the dependency list remaining identical means no breaking changes for users of the previous version, this release likely includes internal tweaks and optimizations. Developers are encouraged to upgrade to Svelte 3.2.0 with the expectation of improved stability and performance without requiring code modifications. Given the identical dependency tree and minor semver bump, the update should be straightforward for existing Svelte projects. Check the official Svelte changelog for exact details of the changes for this version.
All the vulnerabilities related to the version 3.2.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