Svelte version 2.8.0 represents a minor update to the Svelte framework, building upon the foundation laid by version 2.7.2. Both versions share the core philosophy of Svelte: a "magical disappearing UI framework" that shifts work from the browser to compile time, resulting in highly performant web applications. Developers familiar with 2.7.2 will find comfort in the continuity of the API and core concepts in 2.8.0.
Analyzing the package.json data reveals that the primary differences lie in the underlying tooling and release timing. While the devDependencies appear largely identical – encompassing tools like Rollup, TypeScript, ESLint, and Prettier – the updated releaseDate signifies the inclusion of bug fixes, performance tweaks, and potentially minor feature enhancements implemented since the previous release. The slight increase in unpackedSize from 2567942 to 2568154 bytes in version 2.8.0 indicates these small modifications.
For developers, upgrading from 2.7.2 to 2.8.0 should be a relatively straightforward process and is recommended to leverage the latest improvements and stability enhancements. Although the changes are subtle, these increments cumulatively contribute to a smoother development experience and potentially more optimized application performance. Developers should consult the Svelte changelog or release notes for a precise list of changes between the two versions for detailed information. The focus on developer tooling and build process optimization, showcased by the rich devDependencies, remains a key factor in Svelte's appeal, letting developers write more efficiently.
All the vulnerabilities related to the version 2.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