Svelte version 2.14.1 is a minor patch release following closely after version 2.14.0 of the "magical disappearing UI framework." Both versions share the same core description, development dependencies, license (MIT), repository location, and author.
The primary observable differences lie in the dist object and release date. Svelte 2.14.1 was released on October 20, 2018, while version 2.14.0 was released on October 17, 2018, indicating a quick turnaround to address potential issues or optimizations. The unpacked size of version 2.14.1 is marginally larger at 956024 bytes, compared to 955786 bytes in version 2.14.0, with both versions containing 12 files within the package. This subtle size difference usually signifies tiny bug fixes, performance improvements, or minor adjustments in the generated code or supporting assets.
For developers, upgrading from 2.14.0 to 2.14.1 is generally recommended. Although the changes are subtle, patch releases often include important bug fixes that improve overall stability and reliability. These kinds of patch does not come with breaking changes, so upgrading from older versions is safe. Svelte is appreciated for it's magical disappearing act, means that the framework shifts the workload from the browser runtime, to the compilation step, generating highly optimized vanilla Javascript.
All the vulnerabilities related to the version 2.14.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