Svelte, a "magical disappearing UI framework," saw a minor version bump from 1.13.4 to 1.13.5 on April 2nd, 2017. While the core description remains consistent, indicating a focus on the framework's unique approach to UI development, the release date difference suggests bug fixes or incremental improvements rather than major feature additions.
Developers relying on Svelte should note that both versions share identical development dependencies. This signifies a stable development environment and consistent tooling across these releases. Svelte's development ecosystem at this time heavily leaned on Babel for ES2015 transformations, Rollup for bundling, and ESLint for code quality. Tools like css-tree, magic-string, and estree-walker indicate a mature approach to parsing and manipulating code, contributing to Svelte's compilation process. The heavy reliance on Babel plugins points toward ensuring compatibility with various JavaScript environments.
The update from 1.13.4 to 1.13.5 is likely a patch release addressing minor issues, and existing Svelte projects should experience a smooth transition. To decide if upgrading is necessary, developers should check the Svelte project's changelog or commit history around this period for specific details on the fixes or improvements included in version 1.13.5. This will help determine relevance to their project's particular use case. The consistent dependency structure assures developers of a seamless experience regarding tooling and build processes.
All the vulnerabilities related to the version 1.13.5 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