Svelte 3.23.0 refines the experience for developers building web applications with its cybernetically enhanced approach. Comparing it to the previous stable version, 3.22.3, reveals subtle but impactful changes. While both share the same core development dependencies, including crucial tools like Rollup, TypeScript, and ESLint, the updated version incorporates under-the-hood improvements leading to a slightly larger unpacked size (3,127,579 bytes vs. 3,121,827 bytes), hinting at internal enhancements and bug fixes. The release date difference indicates active development and continuous improvement. Developers familiar with Svelte will appreciate these incremental updates, which likely address edge cases, improve performance, and refine the overall development workflow. The maintainers focused on stability also ensured that the core devDependencies versions remain consistent, avoiding breaking changes in build processes. This means projects can easily upgrade to the latest version without worrying about widespread compatibility issues. The new release embodies Svelte's commitment to providing a smooth and polished experience for creating reactive, high-performance web apps, making it a compelling choice for developers seeking a modern and efficient framework. The consistent use of industry-standard tools showcases Svelte's adherence to established best practices.
All the vulnerabilities related to the version 3.23.0 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