Svelte version 1.6.5 is a minor update to the "magical disappearing UI framework," following closely on the heels of version 1.6.4. Both versions share the same core description, dependencies, and development dependencies, indicating a focus on stability and incremental improvements. Crucially, both rely on magic-string for source code manipulation, a critical library for Svelte's compilation process. The development dependencies are extensive, covering testing (mocha, jsdom, nyc), linting (eslint), module bundling (rollup), and code coverage (codecov, babel-plugin-istanbul), suggesting a robust development and testing pipeline.
The key difference between the two versions is the release date, with 1.6.5 released just hours after 1.6.4. This implies that version 1.6.5 likely contains bug fixes or minor tweaks addressing immediate issues found in the previous release. For developers using Svelte, this quick turnaround is reassuring, demonstrating active maintenance and responsiveness from the Svelte team. While the specific changes aren't detailed, upgrading from 1.6.4 to 1.6.5 is recommended to ensure the most stable and reliable experience. Svelte, even in these older versions, empowers developers to build performant web applications by shifting work from runtime to compile time, resulting in smaller, faster code. The MIT license ensures freedom and flexibility in usage, and Rich Harris's authorship lends credibility to the project. Developers should consult the Svelte changelog for a comprehensive list of changes between versions.
All the vulnerabilities related to the version 1.6.5 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