Svelte version 1.58.4 is a minor patch release following closely after 1.58.3 in the Svelte UI framework. Both versions share the same core description: "The magical disappearing UI framework," emphasizing Svelte's compile-time approach to building user interfaces, resulting in highly performant and lightweight applications. They also boast identical development dependencies, encompassing tools for testing (mocha, jsdom, nyc), linting (eslint), bundling (rollup), and TypeScript support, showcasing a robust development environment.
The key differences lie mainly in bug fixes and minor improvements. Developers will appreciate the subtle changes in the unpacked size within the "dist" object between the two versions (2326259 bytes for 1.58.4 versus 2326043 bytes for 1.58.3), that is indicative of small adjustments . More importat the release time is very close: the version 1.58.3 was released on 2018-03-27 and the version 1.58.4 on 2018-03-28.
For developers already using Svelte, upgrading from 1.58.3 to 1.58.4 likely entails incorporating minor fixes that may incidentally address specific edge cases or performance bottlenecks encountered in their projects. While the dependency list remains consistent, reflecting stability in the development toolchain, users are encouraged to review the changelog to understand the precise nature of improvements implemented in version 1.58.4.
All the vulnerabilities related to the version 1.58.4 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