Svelte version 1.6.2 introduces subtle refinements over its predecessor, 1.6.1, offering incremental improvements for developers utilizing this "magical disappearing UI framework." Both versions share the core characteristic of compiling away, resulting in highly performant and efficient JavaScript. The magic-string dependency, crucial for source code manipulation, remains consistent at version ^0.19.0, indicating no fundamental changes to Svelte's code transformation process.
However, the development dependencies showcase key updates that can tangibly impact developers. Notably, nyc (code coverage tool) jumps from version 9.0.1 to 10.0.0. acorn (JavaScript parser), jsdom (JavaScript DOM implementation), mocha (JavaScript testing framework) and rollup (module bundler) go from version 4.0.3 to 4.0.4, from 9.8.3 to 9.9.1, from 3.1.2 to 3.2.0 and from 0.36.3 to 0.39.0 respectively. These upgrades suggest improvements in testing environments, code analysis and module bundling capabilities. reify, responsable for live code reloading, goes from 0.4.0 to 0.4.4 suggesting bug fixes and improvements. source-map-support goes as well from 0.4.6 to 0.4.8, that means better debugging. Furthermore there are also improvements on eslint, rollup-plugin-buble and rollup-plugin-commonjs. While the core functionality remains relatively stable, these enhancements collectively contribute to a more robust and developer-friendly experience by providing better tooling and potentially addressing existing bugs or performance bottlenecks. Developers upgrading will likely benefit from more accurate testing, improved code analysis, and potentially faster build times.
All the vulnerabilities related to the version 1.6.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