Svelte 1.60.0 represents a minor version update over its predecessor, Svelte 1.59.0, within the rapidly evolving Svelte ecosystem. Both versions share the core functionality of being a "magical disappearing UI framework," emphasizing the compiler's ability to transform declarative code into highly efficient vanilla JavaScript at build time, resulting in performant web applications. The developer experience remains consistent, with both versions drawing upon a similar set of development dependencies. These include tools like Rollup for bundling, Typescript for type checking, eslint for code formatting and many others to facilitate a robust and productive development workflow. Dependency versions appear mostly identical, so no tool version upgrade occurred.
A notable difference lies in the unpacked size of the distributed package, with version 1.60.0 being slightly larger (2354336 bytes) than version 1.59.0 (2329093 bytes). This increase, although minor, could reflect the addition of new features, bug fixes, or performance improvements within the Svelte compiler or runtime. Developers considering upgrading from 1.59.0 to 1.60.0 can expect a seamless transition, as the core API and development practices are likely unchanged. Svelte continues to prioritize developer experience and performance, solidifying itself as a compelling choice for modern web development. The relatively small changes between versions suggests that important work happened under the hood and only a detailed changelog can reveal exact modifications.
All the vulnerabilities related to the version 1.60.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