Svelte 3.6.1 is a minor update following closely on the heels of Svelte 3.6.0, both versions delivering on the promise of cybernetically enhanced web app development. For developers already using Svelte, the transition should be seamless. Examining the package data reveals key similarities: both versions maintain the same core description, dependencies, license (MIT), repository details, and author. This signifies that the fundamental framework and its philosophy remain consistent.
The devDependencies also remain nearly identical, indicating no major shifts in the tooling ecosystem used for development and testing of the Svelte library itself. This stability is a positive sign for developers, minimizing the need to update their build processes or development environments when upgrading.
Subtle differences exist in the dist section. Version 3.6.1 has one less file yet a slightly increased unpacked size compared to 3.6.0, hinting at internal rearrangements or optimizations. More importantly, 3.6.1 was released shortly after 3.6.0. This quick turnaround often signifies a bug fix or a minor enhancement addressing an immediate issue found in the preceding release. Consequently, upgrading to 3.6.1 is a recommended practice for developers seeking the most stable and refined experience within the 3.6.x series, ensuring they benefit from the latest improvements and potential bug resolutions without introducing disruptive changes. For those starting new Svelte projects, opting for version 3.6.1 provides the most current foundation.
All the vulnerabilities related to the version 3.6.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