Svelte version 1.57.2 is a minor update to the popular "magical disappearing UI framework," building upon the foundation laid by version 1.57.1. Both versions share the same core set of development dependencies, indicating a consistent build and testing environment. Developers utilizing Svelte will find familiar tools like Rollup for bundling, ESLint for code linting, and TypeScript for type checking, ensuring code quality and maintainability. The consistent use of these tools across versions suggests a stable development workflow.
A key indicator of the incremental nature of this upgrade can be seen when comparing the unpacked size of the distributed package, with version 1.57.2 having 2413336 bytes and version 1.57.1 having 2413013 these values indicating a relatively small difference. This most likely implies that the update focuses on bug fixes or minor improvements rather than large feature additions.
For developers, this suggests a safe upgrade path with minimal risk of breaking changes. While the core feature set remains largely unchanged, staying up-to-date ensures access to the latest bug fixes and performance enhancements. Both versions are licensed under the MIT license, offering flexibility and freedom in their use. The release dates of March 12, 2018, for version 1.57.2 and March 9, 2018, for version 1.57.1, further emphasize the proximity of these releases and the likely focus on addressing immediate issues or edge cases.
All the vulnerabilities related to the version 1.57.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