Svelte version 1.18.2 represents a minor update to the popular "magical disappearing UI framework," building upon version 1.18.1. Examining the package.json files of both versions reveals that the core development dependencies remain identical. This suggests that the changes introduced in 1.18.2 likely focus on internal bug fixes, performance improvements, or minor feature enhancements rather than significant API alterations or dependency upgrades. Developers should anticipate a smooth transition from 1.18.1 to 1.18.2, with minimal code adjustments required.
The unchanged development dependencies indicate a consistent development environment and toolchain. Key tools such as rollup for bundling, babel for transpilation, eslint for linting, and mocha for testing retain their respective versions, ensuring continued compatibility and stability. This is highly relevant for developers as it means their existing workflows and build processes shouldn't be disrupted by the update. The release date difference, a span of roughly five days, suggests a quick turnaround addressing potential issues found in the previous version or a rapid implementation of small improvements. To fully understand the specific changes, developers should consult the official Svelte changelog or release notes for 1.18.2, available on the Svelte GitHub repository. While seemingly small, these point releases are essential for maintaining a stable and efficient development experience.
All the vulnerabilities related to the version 1.18.2 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