GHSA-J386-3444-QGWG
Vulnerability from github – Published: 2025-01-03 16:29 – Updated: 2025-01-03 19:26The Trix editor, versions prior to 2.1.11, is vulnerable to XSS when pasting malicious code in the link field.
Impact
An attacker could trick the user to copy&paste a malicious javascript: URL as a link that would execute arbitrary JavaScript code within the context of the user's session, potentially leading to unauthorized actions being performed or sensitive information being disclosed.
See https://gist.github.com/th4s1s/3921fd9c3e324ad9a3e0d846166e3eb8
Patches
Update Recommendation: Users should upgrade to Trix editor version 2.1.12 or later.
Workarounds
This is not really a workaround but something that should be considered in addition to upgrading to the patched version. If affected users can disallow browsers that don't support a Content Security Policy, then this would be an effective workaround for this and all XSS vulnerabilities. Set CSP policies such as script-src 'self' to ensure that only scripts hosted on the same origin are executed, and explicitly prohibit inline scripts using script-src-elem.
References
https://gist.github.com/th4s1s/3921fd9c3e324ad9a3e0d846166e3eb8
Credits
This vulnerability was reported by Hackerone researcher https://hackerone.com/lio346?type=user
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "trix"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.1.12"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-21610"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2025-01-03T16:29:58Z",
"nvd_published_at": "2025-01-03T17:15:09Z",
"severity": "MODERATE"
},
"details": "The Trix editor, versions prior to 2.1.11, is vulnerable to XSS when pasting malicious code in the link field.\n\n### Impact\n\nAn attacker could trick the user to copy\u0026paste a malicious `javascript:` URL as a link that would execute arbitrary JavaScript code within the context of the user\u0027s session, potentially leading to unauthorized actions being performed or sensitive information being disclosed.\n\nSee https://gist.github.com/th4s1s/3921fd9c3e324ad9a3e0d846166e3eb8\n\n### Patches\n\nUpdate Recommendation: Users should upgrade to Trix editor version 2.1.12 or later.\n\n### Workarounds\n\nThis is not really a workaround but something that should be considered in addition to upgrading to the patched version. If affected users can disallow browsers that don\u0027t support a Content Security Policy, then this would be an effective workaround for this and all XSS vulnerabilities. Set CSP policies such as script-src \u0027self\u0027 to ensure that only scripts hosted on the same origin are executed, and explicitly prohibit inline scripts using script-src-elem.\n\n### References\n\nhttps://gist.github.com/th4s1s/3921fd9c3e324ad9a3e0d846166e3eb8\n\n### Credits\n\nThis vulnerability was reported by Hackerone researcher https://hackerone.com/lio346?type=user",
"id": "GHSA-j386-3444-qgwg",
"modified": "2025-01-03T19:26:14Z",
"published": "2025-01-03T16:29:58Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/basecamp/trix/security/advisories/GHSA-j386-3444-qgwg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-21610"
},
{
"type": "WEB",
"url": "https://github.com/basecamp/trix/commit/180c8d337f18e1569cea6ef29b4d03ffff5b5faa"
},
{
"type": "WEB",
"url": "https://github.com/basecamp/trix/commit/c4f0d6f80654603932af6685694f694e96593b93"
},
{
"type": "WEB",
"url": "https://gist.github.com/th4s1s/3921fd9c3e324ad9a3e0d846166e3eb8"
},
{
"type": "PACKAGE",
"url": "https://github.com/basecamp/trix"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Trix allows Cross-site Scripting via `javascript:` url in a link"
}
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
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
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.