GHSA-3QXH-P7JC-5XH6
Vulnerability from github – Published: 2025-02-25 17:49 – Updated: 2025-02-25 17:49Inserts/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.
```js
const [text] = createResource(() => {
return new URL(getRequestEvent().request.url).searchParams.get("text");
});
return ( <> Text: {text()} </> ); ```
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "solid-js"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.9.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-27109"
],
"database_specific": {
"cwe_ids": [
"CWE-116",
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2025-02-25T17:49:40Z",
"nvd_published_at": "2025-02-21T22:15:14Z",
"severity": "HIGH"
},
"details": "Inserts/JSX expressions inside illegal inlined JSX fragments lacked escaping, allowing user input to be rendered as HTML when put directly inside JSX fragments.\n\nFor instance, `?text=\u003csvg/onload=alert(1)\u003e` would trigger XSS here.\n```js\n const [text] = createResource(() =\u003e {\n return new URL(getRequestEvent().request.url).searchParams.get(\"text\");\n });\n\n return (\n \u003c\u003e\n Text: {text()}\n \u003c/\u003e\n );\n ```",
"id": "GHSA-3qxh-p7jc-5xh6",
"modified": "2025-02-25T17:49:40Z",
"published": "2025-02-25T17:49:40Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/solidjs/solid/security/advisories/GHSA-3qxh-p7jc-5xh6"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-27109"
},
{
"type": "WEB",
"url": "https://github.com/solidjs/solid/commit/b93956f28ed75469af6976a98728e313d0edd236"
},
{
"type": "PACKAGE",
"url": "https://github.com/solidjs/solid"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "Solid Lacks Escaping of HTML in JSX Fragments allows for Cross-Site Scripting (XSS)"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.