Svelte versions 1.13.2 and 1.13.1, both described as "The magical disappearing UI framework," showcase incremental improvements for developers seeking a performant and streamlined front-end experience. While the core promise remains consistent, a notable difference lies in the dependency management. Version 1.13.1 explicitly lists magic-string as a dependency, while 1.13.2 moves it (implicitly or explicitly) to the devDependencies. This could imply internal build process optimizations or a shift in how magic-string is utilized during development versus production.
Both versions share a substantial number of devDependencies, essential for development workflows. These include tools like rollup for bundling, babel for transpilation, eslint for code linting, and mocha for testing. The presence of various Babel plugins indicates a focus on ensuring compatibility with older JavaScript environments by transforming modern ES2015+ features. The consistent use of these tools signifies stability in the development environment for Svelte projects built using either version. Other worth mentioning libs are css-tree used for CSS parsing and manipulation and fuzzyset.js which implements fuzzy string matching.
The upgrade from 1.13.1 to 1.13.2 might involve bug fixes, performance tweaks, or refinements in the compiler that converts Svelte components into highly efficient vanilla JavaScript. It's advisable for developers to consult the official Svelte changelog for detailed specifics. The packages are licensed under MIT license and developed by Rich Harris, the main contributor.
All the vulnerabilities related to the version 1.13.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