Astro: Reflected XSS via unescaped slot names in @astrojs/solid-js
Summary
The @astrojs/solid-js renderer wraps named slot content passed to Solid components in an <astro-slot> element, and writes the slot name into its name attribute without HTML escaping. A slot name containing " could end the attribute and inject arbitrary HTML into the page.
For example, a page that takes a slot name from the request:
---
import Tabs from '../components/Tabs.jsx';
const tab = Astro.url.searchParams.get('tab');
---
<Tabs client:load active={tab}><div slot={tab}>…</div></Tabs>
rendered with a Solid component that renders a slot by name:
export default function Tabs(props) {
return <div>{props[props.active]}</div>;
}
would output a tab value such as x"><img src=x onerror=alert(1)> as live HTML.
Impact
Reflected cross-site scripting. An attacker who gets a user to open a crafted link can run JavaScript on the site's origin, but only in applications where all of the following are true:
- The page passes request-controlled input (such as a query parameter) as a slot name.
- The Solid component is hydrated with a
client:*directive. For non-hydrated components the slot wrapper is removed from the output, together with itsnameattribute. - The Solid component renders the attacker-chosen slot, which in practice means accessing slot props by a dynamic name. Components that never render the slot only output Astro's already escaped fallback template.
This is the @astrojs/solid-js counterpart of GHSA-8hv8-536x-4wqp (CVE-2026-50146), which fixed the same issue in astro core.
Affected versions
@astrojs/solid-js >= 0.2.0, <= 7.1.1.
Patches
Fixed in @astrojs/solid-js 7.1.2. Slot names are now HTML-escaped in the server renderer.
Workarounds
Upgrade to @astrojs/solid-js 7.1.2 or later. Before upgrading, do not use request-controlled input as a slot name, or map it to a fixed set of known slot names before passing it to a component.
Credits
Reported by @manus-pi.
Betroffene Software
Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.
| Plattform | Paket | Anfällige Versionen | Behoben in |
|---|---|---|---|
| npm-Paket | @astrojs/solid-js | >= 0.2.0, < 7.1.2 | 7.1.2 |
Verweise
- CVSS-Vektor
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N- Schwäche (CWE)
CWE-79- Plattform
- npm
- Paket
@astrojs/solid-js- Veröffentlicht
- 12.11.2026
- Aktualisiert
- 13.11.2026 00:17
Quellen und Lizenzen
OSV / GitHub Advisory Database - GHSA-jmv2-qgxf-f995 - CC BY 4.0
Schwachstellenhistorie: @astrojs/solid-js
Alle veröffentlichten Schwachstellen dieses Pakets (npm-Paket), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.
Dies ist die einzige bekannte Schwachstelle dieses Pakets.
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.