Svelte version 1.58.3 is a minor patch release following 1.58.2 in the popular "disappearing UI framework". Both versions share the same core description and maintain the MIT license, ensuring continued free and open-source use. Examining the package.json files reveals that the development dependencies remain identical, meaning that the tools used for building, testing, and linting the library haven't changed between these versions. This includes crucial tools such as Rollup for bundling, Typescript for type checking, and ESLint for code linting, ensuring consistent development practices.
The most notable differences lie in the dist section. The releaseDate shows that version 1.58.3 was released on March 27, 2018, shortly after 1.58.2 released on March 24, 2018, indicating a quick turnaround, likely to address a specific bug or issue. Both versions package 11 files, but the unpackedSize of 1.58.3 is slightly smaller at 2326043 bytes compared to 2326131 bytes in 1.58.2. This suggests that the patch likely included small optimizations or code reductions. For developers, upgrading from 1.58.2 to 1.58.3 is recommended, as it incorporates potential bug fixes and minor improvements without introducing breaking changes, ensuring a smoother development experience. The core functionalities of Svelte, which revolve around writing declarative components that compile to highly efficient vanilla JavaScript, remain consistent across these versions.
All the vulnerabilities related to the version 1.58.3 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