Svelte version 1.4.0, released on December 18, 2016, refines the "magical disappearing UI framework" building upon version 1.3.1, released just a day prior. While both versions share the same core description, dependencies on magic-string, MIT license, repository details, and author (Rich Harris), the updated version signifies improvements and bug fixes implemented within a short timeframe. For developers, this quick iteration suggests active development and responsiveness from the Svelte team. The devDependencies, including tools such as rollup for bundling, eslint for linting, and mocha for testing, remain consistent, ensuring continuity in the development workflow. The minor version bump from 1.3.1 to 1.4.0 signals that the changes are likely to be backward-compatible, posing minimal disruption for those already using Svelte. Developers can anticipate performance enhancements, refined features, or resolutions to previously identified issues. The release date difference highlights Svelte's commitment to iterative improvements and addressing user concerns promptly. Staying current with the latest minor version is a prudent choice, as it equips developers with the most up-to-date, polished, and reliable tools for crafting efficient web applications. Ensure reading the release notes to get clear understanding about the changes.
All the vulnerabilities related to the version 1.4.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