Svelte versions 1.13.2 and 1.13.3, both described as "The magical disappearing UI framework," represent incremental improvements in this innovative approach to web development. The core promise of Svelte, to shift work from the browser to the compile step, remains consistent. Examining the package manifests, the primary difference between the two versions lies in their release dates. Version 1.13.3 was published on April 2, 2017, while version 1.13.2 was released a few days earlier, on March 29, 2017.
A closer look reveals that the devDependencies remains identical between the two versions. This suggests that the core dependencies and tooling used for development, testing, and building Svelte itself were unchanged during that period. Developers utilizing Svelte can still expect the same robust ecosystem of tools like Rollup for bundling, Babel for ES2015+ transpilation, ESLint for code linting, and Mocha for testing. The consistent dependency versions indicate that the update likely involves bug fixes, performance enhancements, or minor feature tweaks within the Svelte compiler and runtime, rather than major architectural changes.
For developers considering using Svelte, the key takeaway is the stability and maturity of the toolchain. The framework utilizes a comprehensive suite of modern JavaScript tools, ensuring compatibility with existing workflows. While the specific changes from 1.13.2 to 1.13.3 are not explicitly detailed in the manifests, the consistent devDependencies inspire confidence in the ongoing development and maintenance of the Svelte ecosystem. Developers can expect a smooth and efficient development experience, empowered by the framework's core strengths: writing concise, declarative code that compiles down to highly optimized vanilla JavaScript, resulting in fast and lightweight web applications.
All the vulnerabilities related to the version 1.13.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