Svelte 3.6.8 is a minor patch release following 3.6.7, addressing underlying improvements and bug fixes rather than introducing major new features. Both versions, "Cybernetically enhanced web apps", share the same core architecture and functionalities that define Svelte: a compiler that transforms declarative components into highly efficient JavaScript, surgically updating the DOM.
Developers using Svelte will find version 3.6.8 a stable upgrade, focusing on refining the existing developer experience and runtime performance. Examining the devDependencies reveals the toolchain utilized for development and testing remains largely consistent between the two versions, indicating a focus on stability. A notable change is the specific version of @types/node: version 3.6.7 depends on version 12, while version 3.6.8 depends on version 8. While both versions rely on core dependencies like rollup for bundling, typescript for type checking, and eslint for code linting, ensuring a robust and modern development environment, Svelte 3.6.8 moves a step back regarding node versions.
While the core feature set remains the same, Svelte 3.6.8 includes vital refinements that lead to a smoother development process. Developers should update to benefit from these subtle enhancements and fixes, ensuring compatibility and future-proofing their Svelte applications. The focus remains consistent: write less code, and let the compiler do the heavy lifting.
All the vulnerabilities related to the version 3.6.8 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