Svelte versions 1.15.0 and 1.15.1 represent incremental updates to the "magical disappearing UI framework," focusing primarily on refinements rather than groundbreaking features. Both versions share the same core development dependencies, indicating a consistent build and testing environment. Developers leveraging Svelte can expect a similar experience in terms of tooling and required build processes between these versions. Key dependencies remain consistent including Rollup for bundling, Babel for JavaScript transpilation, and ESLint for code linting.
The most noticeable difference lies in the release date. Version 1.15.1 arrived just a few days after 1.15.0, suggesting that the later version addresses bug fixes or minor improvements identified shortly after the initial release. Given the shared dependency list, developers can infer that no significant dependency upgrades or feature additions were introduced between these versions. Those using Svelte are advised to upgrade to the latest patch version (1.15.1) to benefit from any potential fixes.
For developers evaluating Svelte, these versions exemplify the framework's commitment to iterative improvement and stability. Svelte distinguishes itself by shifting work from the browser to the compile step, resulting in highly performant and lightweight web applications. While these specific versions highlight incremental changes, the consistent dependency stack ensures a stable development experience. The presence of testing tools like Mocha and code coverage tools like Codecov further suggests a dedication to code quality and reliability attracting serious developers.
All the vulnerabilities related to the version 1.15.1 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