Svelte version 1.57.4 represents a minor iteration over the preceding 1.57.3, both versions uphold Svelte's core promise of a "magical disappearing UI framework," abstracting away boilerplate and maximizing performance. Examining the metadata, the primary difference lies in the release date and unpacked size, with 1.57.4 released on March 15, 2018, and version 1.57.3 released just two days prior, on March 13, 2018. The unpacked size for 1.57.4 increased marginally to 2411767 bytes from 2411279 bytes for 1.57.3, indicating possible bug fixes, very minor feature adjustments, optimisations or documentation updates.
Developers should note that while the core dependencies listed in devDependencies remain consistent between the two versions, subtly updated tooling or build processes might result from the differences in unpacked size. For stability, sticking to a specific version is vital; however, adopting 1.57.4 offers the possibility of benefitting from the latest refinements addressed within those two days. Before upgrading from 1.57.3, reviewing the Svelte changelog for that period is highly encouraged to grasp the implications of incorporated fixes or minor adjustments. Both versions depend on a wide arrange of dev dependencies such as rollup, typescript and eslint which are used to build this lean and mean framework.
All the vulnerabilities related to the version 1.57.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