Svelte version 1.62.0 represents a minor update over its predecessor, 1.61.0, offering incremental improvements and bug fixes to the "magical disappearing UI framework." While the core functionality remains consistent, developers can expect a slightly refined experience. The devDependencies are identical, meaning no underlying toolchain changes impact the build or development process. The most noticeable difference lies in the dist object. Version 1.62.0 has a slightly larger unpacked size of 2409823 bytes compared to 1.61.0's 2380939 bytes, suggesting optimizations, new features, or bug fixes have been added leading to an increased package size of few kilobytes. This increase is not drastic, but developers should be aware that upgrading might subtly impact initial load times or bundle sizes, especially in large applications. The release date also highlights the recency of the update, with version 1.62.0 being released a day later that the previous one. For developers already using Svelte, upgrading to 1.62.0 is recommended to benefit from the latest fixes and optimizations. New users will find either version a solid starting point, with 1.62.0 offering the most up-to-date experience. Before upgrading, carefully review the Svelte changelog or release notes for detailed information on specific changes, bug fixes, and potential breaking changes. This ensures a smooth transition and maximizes the benefits of the update.
All the vulnerabilities related to the version 1.62.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