Svelte version 1.46.0 arrives closely after 1.45.0, offering developers the latest refinements to this "magical disappearing UI framework." While the core description remains consistent, the update signifies ongoing development and commitment to improvement. Examining the devDependencies, both versions share an extensive toolkit, showcasing a dedication to comprehensive testing, linting, and build processes. This robust development environment translates to increased stability and reliability for developers leveraging Svelte in their projects. Key tools like rollup for bundling, typescript for static typing, and eslint for code quality are prominently featured, assuring developers of a modern and well-supported ecosystem.
The update from 1.45.0 to 1.46.0, released just two days apart, suggests the newer version likely incorporates bug fixes, performance enhancements, or minor feature additions rather than a ground-breaking overhaul. The unchanged devDependencies list points toward internal improvements and stabilization efforts. For developers, this means a smoother experience and potentially better performance without requiring significant code changes. This continuous improvement cycle makes Svelte a compelling choice for building efficient and maintainable web applications. To harness the enhancements, upgrading to 1.46.0 is recommended.
All the vulnerabilities related to the version 1.46.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