Summary
References
The XSS vulnerability was reported by HackerOne researcher hiumee.
Impact
The Trix editor, in versions prior to 2.1.15, is vulnerable to XSS attacks when pasting malicious code.
An attacker could trick a user to copy and paste malicious code 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.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Update Recommendation: Users should upgrade to Trix editor version 2.1.15 or later.
Frequently Asked Questions
- What is CVE-2025-46812? CVE-2025-46812 is a low-severity cross-site scripting (XSS) vulnerability in trix (npm), affecting versions < 2.1.15. It is fixed in 2.1.15. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of trix are affected by CVE-2025-46812? trix (npm) versions < 2.1.15 is affected.
- Is there a fix for CVE-2025-46812? Yes. CVE-2025-46812 is fixed in 2.1.15. Upgrade to this version or later.
- Is CVE-2025-46812 exploitable, and should I be worried? Whether CVE-2025-46812 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-46812 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-46812? Upgrade
trixto 2.1.15 or later.