Svelte version 1.46.1 is a minor patch release following version 1.46.0 of the "magical disappearing UI framework." Both versions share the same core description, developer dependencies, license (MIT), repository details (hosted on GitHub under sveltejs/svelte), and author (Rich Harris). Examining the developer dependencies, both versions leverage a robust toolchain for development, testing, and building. This includes tools like Rollup for bundling, TypeScript for type checking, ESLint for code linting, and Mocha for testing. Key dependencies for Svelte's internal workings, such as css-tree, magic-string, and estree-walker, are consistently present, indicating a stable core architecture.
The primary visible difference between the two versions lies in their release dates. Version 1.46.1 was published on December 10, 2017, while version 1.46.0 was released on December 9, 2017. Such a short timeframe between releases typically suggests that version 1.46.1 likely addresses a critical bug fix or minor improvement discovered shortly after the 1.46.0 release. While the specifics of the changes aren't explicitly detailed in the metadata, developers using Svelte are encouraged to upgrade to the latest patch version (1.46.1) to benefit from any potential bug fixes that improve stability and reliability. The consistent set of dev dependencies confirms the toolchain's stability for Svelte development. This makes it a reliable choice for front-end projects, as it demonstrates ongoing maintenance and attention to detail from the Svelte team.
All the vulnerabilities related to the version 1.46.1 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