Svelte version 1.58.2 is a minor update to the magical disappearing UI framework, building upon version 1.58.1. Both versions share the same core philosophy, aiming to provide a performant and efficient way to build web applications. They utilize a similar set of development dependencies, ensuring a consistent development experience with tools like Rollup for bundling, ESLint for linting, and TypeScript for enhanced code quality.
However, the key difference lies in the internal improvements and bug fixes incorporated in the newer 1.58.2 release. While the list of devDependencies remains identical, suggesting no major tooling changes, the unpacked size of the newer version is slightly smaller (2326131 bytes vs 2401234 bytes). This indicates optimizations have occurred, likely involving code reduction or more efficient asset handling. The release dates also highlight the timeframe; version 1.58.2 was published just minutes after 1.58.1.
For developers using Svelte, this implies a smooth transition. Upgrading to 1.58.2 should be straightforward, bringing potential performance gains and resolutions to known issues present in version 1.58.1, without any breaking changes. Both versions offer a component-based approach to UI development, compiling code to highly optimized vanilla JavaScript at build time, resulting in smaller bundle sizes and faster runtime performance compared to traditional frameworks. Developers who value incremental improvements and a polished experience will find the update beneficial.
All the vulnerabilities related to the version 1.58.2 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