Svelte, the "magical disappearing UI framework," saw a notable update between version 0.2.2 and 0.3.0. Both versions, licensed under MIT, showcase a commitment to lightweight and efficient UI development, championed by Rich Harris. The core description remains the same, emphasizing its unique approach to building web applications.
Examining the devDependencies, we observe subtle but potentially impactful changes. While most dependencies remain consistent, a key difference emerges with the addition of fuzzyset.js in version 0.3.0. This suggests the introduction of fuzzy string matching capabilities, which might be used for improved developer tooling, enhanced user input handling, or more intelligent component searching.
Furthermore the rollup-plugin-commonjs dependency is removed in version 0.3.0. This could signify internal changes in how Svelte handles CommonJS modules, possibly indicating a shift towards a more modern module system approach or improvements in the bundling process.
Developers considering Svelte will find version 0.3.0 potentially offering enhanced features related to fuzzy matching and a refined module handling system, improving developer experience and potentially leading to more streamlined and optimized builds. The framework continually evolves, reflecting a dedication to providing a performant, developer-friendly way to create web interfaces. The change in release date is also relevant, showing that it was released roughly one day after the previous version.
All the vulnerabilities related to the version 0.3.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