Svelte version 1.36.0, released on September 3, 2017, followed closely on the heels of version 1.35.0, released just two days prior on September 1, 2017. Both versions of this "magical disappearing UI framework" maintain identical core characteristics, sharing the same project description, license (MIT), repository information, and author. The key distinction lies in the version number and associated release date, indicating incremental updates and fixes.
Developers using Svelte will find a consistent set of development dependencies across both versions, suggesting a stable toolchain. These dependencies include essential tools for building, testing, and linting Svelte components, such as Rollup for bundling, ESLint for code quality, and Mocha for testing. The presence of TypeScript and related plugins highlights Svelte's commitment to supporting modern JavaScript development practices.
While the specific changes between 1.35.0 and 1.36.0 are not explicitly detailed in the provided data, the rapid release cycle strongly suggests that version 1.36.0 incorporates bug fixes, performance improvements, or minor feature enhancements addressing issues identified in the preceding version. Developers should consult the official Svelte changelog or release notes for a comprehensive understanding of the precise modifications contained within version 1.36.0 to ensure optimal performance and stability in their projects. The quick turnaround between releases signals an active development team dedicated to refining and improving the Svelte experience.
All the vulnerabilities related to the version 1.36.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