Svelte version 2.7.2 is a minor release following version 2.7.1 of the "magical disappearing UI framework." Both versions share the same core description and license (MIT), indicating a continued commitment to open-source principles. The author remains Rich Harris, and the project's repository is consistent across both iterations. Developers familiar with the Svelte framework won't find major paradigm shifts between these versions.
A key aspect that developers might find interesting lies in examining the differences in the dist section. Version 2.7.2, released on June 8, 2018, has a slightly smaller unpacked size (2567942 bytes) compared to version 2.7.1 (2568454 bytes), released on June 5, 2018. While seemingly minor, this could reflect optimizations in the compiled output. The fileCount remains constant at 15, suggesting no structural alterations to the package's contents.
The devDependencies remain identical, pointing to consistent tooling and testing practices between the releases. This includes libraries like rollup, typescript, eslint, prettier, and various rollup plugins, indicating a strong focus on modern JavaScript development and code quality. Developers leveraging these same tools in their Svelte projects can anticipate a seamless integration experience. Ultimately, the update likely involves bug fixes documented in the release but not mentioned in provided data.
All the vulnerabilities related to the version 2.7.2 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