How severe is GHSA-mcrw-746g-9q8h?

No CVSS score has been assigned to GHSA-mcrw-746g-9q8h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mcrw-746g-9q8h?

GHSA-mcrw-746g-9q8h affects the following packages: trix (npm). Ecosystems affected: npm.

How do I fix GHSA-mcrw-746g-9q8h?

Update trix to 2.1.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcrw-746g-9q8h is resolved across your whole dependency graph.

How do I detect GHSA-mcrw-746g-9q8h in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trix. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mcrw-746g-9q8h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mcrw-746g-9q8h?

O3 pinpoints whether GHSA-mcrw-746g-9q8h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mcrw-746g-9q8h actively exploited in the wild?

No public exploit code has been indexed for GHSA-mcrw-746g-9q8h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-mcrw-746g-9q8h?

GHSA-mcrw-746g-9q8h is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-mcrw-746g-9q8h published, and has it been updated?

GHSA-mcrw-746g-9q8h was published on May 8, 2025 and was last updated on May 8, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-mcrw-746g-9q8h

Fix: basecamp/trix@7522608

GHSA-mcrw-746g-9q8h is a Cross-site Scripting (XSS) vulnerability in trix. O3 Security confirms whether GHSA-mcrw-746g-9q8h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Trix vulnerable to Cross-site Scripting on copy & paste

Also known asCVE-2025-46812

Published

May 8, 2025

Updated

May 8, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 8, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

trixnpm

517Kdownloads / week

Description

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.

Patches

Update Recommendation: Users should upgrade to Trix editor version 2.1.15 or later.

References

The XSS vulnerability was reported by HackerOne researcher hiumee.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`trix`	all versions	2.1.15

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trix. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update trix to 2.1.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcrw-746g-9q8h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mcrw-746g-9q8h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mcrw-746g-9q8h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ### Patches Update Recommendation: Users should upgrade to Trix editor version 2.1.15 or later. ### References The XSS vulnerability was reported by HackerOne researcher [hiumee](https://hackerone.com/hiumee?type=user).

O3 Security · Impact-Aware SCA

Is GHSA-mcrw-746g-9q8h in your dependencies?

O3 detects GHSA-mcrw-746g-9q8h across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works