Skip to content

Solid Lacks Escaping of HTML in JSX Fragments allows for Cross-Site Scripting (XSS)

High severity GitHub Reviewed Published Feb 21, 2025 in solidjs/solid • Updated Feb 25, 2025

Package

npm solid-js (npm)

Affected versions

< 1.9.4

Patched versions

1.9.4

Description

Inserts/JSX expressions inside illegal inlined JSX fragments lacked escaping, allowing user input to be rendered as HTML when put directly inside JSX fragments.

For instance, ?text=<svg/onload=alert(1)> would trigger XSS here.

  const [text] = createResource(() => {
    return new URL(getRequestEvent().request.url).searchParams.get("text");
  });

  return (
    <>
      Text: {text()}
    </>
  );

References

@ryansolid ryansolid published to solidjs/solid Feb 21, 2025
Published by the National Vulnerability Database Feb 21, 2025
Published to the GitHub Advisory Database Feb 25, 2025
Reviewed Feb 25, 2025
Last updated Feb 25, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

CVE ID

CVE-2025-27109

GHSA ID

GHSA-3qxh-p7jc-5xh6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.