Skip to content
Fencer Vulns
medium 5.4

CVE-2024-34341 json

The Trix Editor Contains an Arbitrary Code Execution Vulnerability

published 2024-05-07 2 y ago modified 2026-06-17 4 mo ago also GHSA-qjqp-xr96-cj99 , EUVD-2024-1747

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Trix is a rich text editor. The Trix editor, versions prior to 2.1.1, is vulnerable to arbitrary code execution when copying and pasting content from the web or other documents with markup into the editor. The vulnerability stems from improper sanitization of pasted content, allowing an attacker to embed malicious scripts which are executed within the context of the application. Users should upgrade to Trix editor version 2.1.1 or later, which incorporates proper sanitization of input from copied content.

Patch / fix

  • npm trix 1.3.2, 2.1.1
  • rubygems actiontext 7.0.8.3, 7.1.3.3
  • basecamp trix 2.1.1
  • rubygem-actiontext-7.0 openSUSE Tumbleweed 7.0.8.6-1.3
  • rubygem-rails-7.0 openSUSE Tumbleweed 7.0.8.6-1.3
  • rubygem-actiontext-7.0 openSUSE Tumbleweed 7.0.8.4-1.1
  • rubygem-rails-7.0 openSUSE Tumbleweed 7.0.8.4-1.1

opensuse advisories openSUSE-SU-2025:15111-1openSUSE-SU-2025:15124-1openSUSE-SU-2024:14068-1openSUSE-SU-2024:14074-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm trix
>=2.0.0, <2.1.1
>=0.9.0, <1.3.2
2.1.1
1.3.2
rubygems actiontext
>=7.0.0.alpha1, <7.0.8.3
>=7.1.0.beta1, <7.1.3.3
7.0.8.3
7.1.3.3

Affected products

  • basecamp trix

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.