Skip to main content
VulnerabilityPublished Updated

CVE-2024-51434: froala-wysiwyg-editor · Cross-site Scripting

Affects froala-wysiwyg-editorSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmfroala-wysiwyg-editorpkg:npm/froala-wysiwyg-editorOther threatsAffected
  • <=4.3.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade: Monitor Froala's official channels for patches or updates addressing this vulnerability and upgrade to a fixed version as soon as it becomes available.
  2. Input Sanitization: Implement robust server-side and client-side input validation and sanitization to neutralize any injected scripts, especially focusing on handling the <plaintext> tag and related HTML elements.
  3. Content Security Policy (CSP): Deploy a strict CSP header to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks.
  4. Output Encoding: Ensure that all user-generated content rendered by the Froala editor is properly encoded before display to prevent script execution.
  5. User Awareness: Educate users about the risks of clicking untrusted links or interacting with suspicious content to reduce the likelihood of successful exploitation.
  6. Web Application Firewall (WAF): Use a WAF with rules designed to detect and block XSS payloads targeting the Froala editor.
  7. Monitoring and Logging: Implement enhanced logging and monitoring to detect anomalous behavior or attempted exploitation attempts related to this vulnerability.
  8. Temporary Workaround: If upgrading is not immediately possible, consider disabling or restricting the use of the <plaintext> tag or limiting editor functionality to reduce attack surface.

Description

Inconsistent <plaintext> tag parsing allows for XSS in Froala WYSIWYG editor 4.3.0 and earlier.

References

Community reviews

Loading reviews…