Svelte version 1.60.1 is a patch release following closely after version 1.60.0, both iterations of the "magical disappearing UI framework." Examining the package metadata reveals minimal changes focused on under-the-hood improvements. Both versions share an identical list of devDependencies, encompassing crucial tools like Rollup for bundling, TypeScript for enhanced code quality, and ESLint for linting. This indicates a consistent development environment across the two versions. The core framework functionalities and the commitment to providing developers with familiar tools like rollup-plugin-typescript and rollup-plugin-node-resolve remain unchanged.
The most notable difference lies within the dist object. While both versions have 11 files in the distributed package, 1.60.1 has a slightly larger unpacked size of 2,354,368 bytes compared to 1.60.0's 2,354,336 bytes – a mere 32 bytes difference. Furthermore, the release date indicates that version 1.60.1 was published on April 3, 2018, shortly after 1.60.0's release on April 1, 2018. This suggests that 1.60.1 likely contains bug fixes or minor adjustments addressing issues discovered immediately after the initial 1.60.0 release. For developers, this translates to a potentially more stable experience with 1.60.1, recommended for new projects or updating existing ones to leverage these quick fixes.
All the vulnerabilities related to the version 1.60.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