Svelte 3.19.0 is a minor version update to the Svelte JavaScript framework, building upon the foundation laid by version 3.18.2. Both versions retain the core promise of "Cybernetically enhanced web apps," offering developers a component-based approach to building performant and modern web applications. Examining the devDependencies reveals largely consistent tooling, suggesting that the update is primarily focused on internal improvements, bug fixes, and potentially new features rather than a significant overhaul of the development environment.
While the specific changelog details are not provided in the metadata, the increase in unpackedSize from 3,074,125 to 3,081,594 bytes hints at the addition of new code or assets. Depending on the changes, developers might experience enhanced performance, improved developer experience, or access to new functionalities. Upgrading to Svelte 3.19.0 is likely a low-risk operation given the shared devDependencies and minor version bump but keep an eye out for details about features and bug fixes. The release date difference emphasizes the active development and maintenance of the Svelte framework. Always consult official Svelte documentation and release notes for a comprehensive understanding of the changes and potential migration considerations when upgrading between versions.
All the vulnerabilities related to the version 3.19.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