Svelte 3.14.1 represents a minor update over version 3.14.0, offering refinements and bug fixes to the core Svelte framework. Both versions share the same fundamental description: "Cybernetically enhanced web apps," underscoring Svelte's commitment to building performant and efficient web applications. The key difference between the two versions resides in their internal tooling and build process, reflected in the changes to the devDependencies and the dist object. Noticeably, code-red jumped from version 0.0.20 to version 0.0.21 in the newer release. The file counts and unpacked size within the dist object also differ slightly, indicating adjustments to the bundled distribution. Version 3.14.0 has 252 files with unpacked size of 3023438, while Version 3.14.1 has 204 files and 3002650 unpacked size. This reduction in size typically means streamlined code or removal of unnecessary assets, potentially leading to faster load times for developers. Both versions maintain the same core dependencies for development, including tools like Rollup, TypeScript, and various ESLint plugins, ensuring a consistent development environment across these minor releases. For developers, upgrading from 3.14.0 to 3.14.1 promises primarily stability improvements.
All the vulnerabilities related to the version 3.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