Svelte 3.44.0 represents a minor version bump, arriving shortly after version 3.43.2. Both versions cater greatly towards developers looking for an efficient, cybernetically enhanced approach to building web applications. The core description remains consistent: Svelte aims to provide a streamlined way to create reactive and highly performant user interfaces by shifting the workload from the browser to the compilation step.
Examining the devDependencies suggests stability in the toolchain. The listed dev dependencies stay consistent between 3.43.2 and 3.44.0, indicating minimal impact on the developer experience. This signifies ongoing effort to maintain the existing developer workflow and ecosystem compatibility such as testing, linting, and build processes.
A minimal difference is observed in the dist section of the package data. The fileCount increased from 233 to 234, and unpackedSize increased from 6936445 to 6942238 bytes. This could imply minor bug fixes, enhancements, or small feature additions in the core compiler or runtime. While not explicitly detailed, the update suggests a focused commitment to maintenance and incremental improvement. The release date difference highlights the active development of the Svelte framework. In summary, upgrading from 3.43.2 to 3.44.0 should be a smooth transition, primarily offering under-the-hood improvements rather than breaking API changes.
All the vulnerabilities related to the version 3.44.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