Svelte 1.7.0 marks a subtle evolution from version 1.6.11, offering developers a potentially more refined experience with this "magical disappearing UI framework." While the core dependencies, like magic-string, remain consistent, a closer look reveals the incremental improvements that define this update. Both versions share an identical suite of development dependencies, encompassing tools for testing (mocha, nyc, jsdom), linting (eslint), bundling (rollup), code coverage (codecov), and various utilities for source map generation, AST manipulation, and ES2015 module transformation. This signifies a continued commitment to code quality, developer tooling, and maintaining a consistent development environment. For developers already using Svelte, upgrading to 1.7.0 appears straightforward, with no immediate changes in dependencies to manage.
However, the true essence of this update likely lies in bug fixes and performance enhancements within the Svelte compiler itself; aspects which are not explicitly declared. Svelte advertises itself as a UI framework that compiles away, meaning that the improvements from a new version are not always evident in the package dependencies, but most often impacting the code resulting from the compilation step. Developers should prioritize reviewing the official changelog or release notes for a comprehensive understanding of specific fixes and optimizations. Given the rapid pace of web development, even incremental updates like this can contribute to a smoother developer workflow and improved application performance. It is a signal that the project it's alive and well with consistent (although small) updates.
All the vulnerabilities related to the version 1.7.0 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