Svelte is a UI framework known for its "magical disappearing" act, compiling components into highly efficient vanilla JavaScript during the build process, resulting in smaller bundle sizes and improved runtime performance compared to traditional virtual DOM approaches. Comparing versions 1.1.1 and 1.1.0 highlights the iterative development of this innovative framework. While both share the same core description and licensing under the MIT license, key differences lie in their release dates and potentially include bug fixes or minor improvements implemented between the two releases.
Both versions rely on an extensive suite of development dependencies for tasks like code linting (eslint), bundling (rollup), testing (mocha, jsdom, nyc, codecov), and source map generation. Key dependencies for development also include tools for manipulating and analyzing code like acorn, estree-walker, magic-string and locate-character. Notable dependencies also include rollup plugins like rollup-plugin-buble, rollup-plugin-commonjs, and rollup-plugin-node-resolve, which are crucial for the build process. Babel plugins transform newer JavaScript syntax into a format compatible with older browsers. The minimal difference suggests that version 1.1.1 primarily addresses either minor bug fixes observed in 1.1.0 or potentially incorporates small enhancements to improve build efficiency or developer experience. For developers, it signals the ongoing commitment to stability and optimization within the Svelte ecosystem, advising adoption of the latest patch release in the 1.1 series.
All the vulnerabilities related to the version 1.1.1 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