Svelte version 1.8.0 represents a minor update to the popular "magical disappearing UI framework," building upon the foundation laid by version 1.7.1. While both versions share the same core dependencies, including magic-string for efficient string manipulation, and a suite of developer dependencies aimed at testing, linting, and building the framework, the key difference lies in the release date. Version 1.8.0 was released on March 1st, 2017, signifying bug fixes, performance improvements ,or minor feature additions implemented after the release of 1.7.1 on February 28th, 2017.
For developers using Svelte, this means upgrading from 1.7.1 to 1.8.0 likely offers a more refined and stable experience. While the underlying API and development workflow remain consistent, users can expect potential enhancements in areas like rendering speed, code optimization, or resolution of previously identified issues. The extensive list of devDependencies, encompassing tools like Rollup for bundling, ESLint for code quality, and Mocha for testing, assures developers that Svelte prioritizes a robust development environment . Svelte's commitment to a disappearing framework is further underscored, as the update ensures components are compiled away into highly optimized vanilla JavaScript during build time, resulting in fast and efficient web applications. Upgrading to the latest minor version is advisable to leverage these improvements and maintain a healthy codebase.
All the vulnerabilities related to the version 1.8.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