Svelte 3.2.1 is a minor patch release following version 3.2.0 in the Svelte framework, designed for building cybernetically enhanced web applications. Both versions share the same core development dependencies, indicating a stable development environment and consistent tooling experience. Developers using either version will find familiar tools like Rollup for bundling, TypeScript for type checking, and ESLint for code linting.
The key difference lies in the internal improvements and bug fixes addressed in the newer 3.2.1 release. While the provided data doesn't detail the specific fixes, the slight increase in unpacked size (1,007,183 bytes vs. 1,005,321 bytes) suggests optimizations or additions, probably small bugfixes or performance enhancements. For developers, upgrading to 3.2.1 is recommended to benefit from the latest stability improvements and address any potential minor issues present in 3.2.0. The consistent dependency list ensures a smooth transition with no breaking changes anticipated in the development workflow. Both releases ensure continue to rely on the MIT license, encouraging open-source use and contribution within the Svelte community. Rich Harris remains the author, maintaining the project's vision and trajectory. Release dates indicate active development, with 3.2.1 published shortly after 3.2.0. Developers should check Svelte's official changelog for a comprehensive list of changes in 3.2.1.
All the vulnerabilities related to the version 3.2.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