Svelte version 1.0.4, released shortly after 1.0.3, represents a subtle yet important iteration of the "magical disappearing UI framework." Both versions share the same core philosophy of shifting work from the browser to compile time, resulting in highly efficient and performant web applications. A key factor for developers considering Svelte is its focus on generating small, framework-less vanilla JavaScript bundles that minimize overhead and maximize speed. The developer experience is enhanced by leveraging familiar tools like Rollup for bundling, ESLint for linting, and Mocha for testing, all underscored by a permissive MIT license. The core dependencies, including crucial tools for code transformation and analysis like Acorn, MagicString, and estree-walker, remain consistent.
The negligible gap in release dates suggests 1.0.4 likely addresses bug fixes or minor improvements identified immediately following the initial 1.0.3 release. For developers adopting Svelte, this indicates a commitment to rapid issue resolution and continuous improvement. While specific changes between these versions aren't detailed in the provided data, the implication is that 1.0.4 offers an incrementally more stable and refined experience. Users are encouraged to consult the official Svelte changelog during this timeframe for precise details. In essence, both versions position Svelte as a compelling option for developers prioritizing performance and a streamlined development workflow, with 1.0.4 being the slightly more polished choice.
All the vulnerabilities related to the version 1.0.4 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