Svelte versions 1.6.10 and 1.6.11, both described as the "magical disappearing UI framework," present minimal differences from a developer's perspective. The core functionality and approach of Svelte, focused on compiling components into highly efficient vanilla JavaScript during build time, remains consistent across both versions. Developers can still leverage Svelte's reactive statements, simplified component syntax, and excellent performance for building web applications.
Examining the package.json data reveals no alterations in dependencies. Both versions rely on the same versions of crucial packages like magic-string, and the suite of development dependencies for testing, linting, and building, including rollup, eslint, and various Rollup plugins, are identical. This suggests that the update from 1.6.10 to 1.6.11 likely includes minor bug fixes, performance improvements, or internal refactoring that doesn't impact the public API or require developers to change their code.
The primary difference lies in the releaseDate. Svelte 1.6.11 was released shortly after 1.6.10, indicating a quick patch or refinement. While upgrading is generally recommended to benefit from any fixes or improvements, the similarities suggest that developers already using 1.6.10 won't encounter breaking changes or significant feature additions in 1.6.11. The key takeaway is that Svelte continues its evolution with incremental updates, maintaining stability and developer familiarity.
All the vulnerabilities related to the version 1.6.11 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