Svelte version 1.52.0 arrived on January 19, 2018, building upon the foundation of version 1.51.1, released just days earlier on January 11, 2018. Both versions share the same core description: "The magical disappearing UI framework," highlighting Svelte's key feature of compiling away into highly optimized vanilla JavaScript. Diving into the developer dependencies, which are essential for development and testing, we see a remarkable consistency between the two releases. Every dependency, from nyc and glob to rollup-plugin-node-resolve and typescript, remains at the same version number. This suggests a focus on stability and incremental improvements rather than a sweeping overhaul.
For developers, this means upgrading from 1.51.1 to 1.52.0 is unlikely to introduce breaking changes related to these dependencies. While the core framework itself might contain bug fixes or minor enhancements, the development environment should remain largely unchanged. The consistent dependency versions simplify the upgrade process, reducing the risk of compatibility issues with existing build tools and workflows. Developers can expect a smooth transition, leveraging the same tools and configurations they were already using. The rapid release cycle suggests ongoing maintenance and refinement, giving developers confidence in the continued support and evolution of the Svelte framework.
All the vulnerabilities related to the version 1.52.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