Svelte version 1.0.5 represents a minor iteration over its predecessor, 1.0.4, within the early stages of this "magical disappearing UI framework." Both versions share the same core description, positioning Svelte as a tool that aims to make UI development more efficient by shifting work from runtime to compile time. Examining their package.json files reveals near-identical dependency structures including essential development tools such as rollup and various rollup-plugin-* packages for bundling, eslint for linting, mocha for testing, and babel related tools for transpilation. They depend on the same testing and utility libraries like jsdom, fuzzyset.js, and magic-string. The development dependencies highlight a focus on modern JavaScript development practices and robust testing. The consistent set of dev dependencies suggests that the updates between these versions didn't require any significant changes to the tooling or build process making the migration easier for most of the developers.
The most notable difference lies in their release dates: 1.0.5 was published on December 1, 2016, while 1.0.4 was released on November 30, 2016, indicating a rapid succession. This suggests that version 1.0.5 likely contains bug fixes, minor improvements, or very targeted enhancements identified immediately after v1.0.4 was released, rather than any major feature additions. For developers using Svelte, upgrading from 1.0.4 to 1.0.5 would likely be a low-risk proposition, aimed at ensuring stability and benefiting from recent refinements. Both versions underscore Svelte's MIT license, its GitHub repository for open-source contribution, and Rich Harris as the author.
All the vulnerabilities related to the version 1.0.5 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