Svelte 1.1.0 represents a minor version bump over its predecessor, 1.0.7, in the early days of this "magical disappearing UI framework." Both versions share an identical set of development dependencies, indicating a consistent build and testing environment powered by tools like Rollup, ESLint, Mocha, and others. This suggests that the core development workflow and quality assurance processes remained stable between these releases.
For developers, the upgrade from 1.0.7 to 1.1.0 likely introduced bug fixes and small improvements rather than significant API changes or new features. While the absence of substantial alterations might seem uneventful, it underscores the focus on stability and reliability during this phase of Svelte's maturation. The identical devDependencies list points to a commitment to maintaining code quality and preventing regressions.
The key takeaway for developers considering either version is that 1.1.0 likely offers a more refined and dependable experience. Although the specific changes aren't detailed in the provided metadata, upgrading to the newer minor version is generally recommended for its cumulative enhancements and potential resolution of edge cases encountered in 1.0.7. Developers experimenting with Svelte should note the early stage of the framework at this point, where minimizing breaking API changes and creating a dependable base for upcoming significant advancements was essential.
All the vulnerabilities related to the version 1.1.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