CVE-2024-21911: Cross-site scripting vulnerability in TinyMCE
TinyMCE versions before 5.6.0 are affected by a stored cross-site scripting vulnerability. An unauthenticated and remote attacker could insert crafted HTML into the editor resulting in arbitrary JavaScript execution in another user's browser.
Security readout for executives and security teams
Plain-English summary
TinyMCE before 5.6.0 can store unsafe HTML that later runs JavaScript in another user’s browser. The main business risk is account-session abuse or data exposure inside applications that let untrusted users submit content through TinyMCE.
Executive priority
Treat this as a moderate priority unless TinyMCE is exposed to anonymous or customer-submitted content viewed by staff or administrators; then prioritize remediation promptly.
Technical view
CVE-2024-21911 is a stored cross-site scripting flaw in TinyMCE before 5.6.0. The CVSS 3.1 score is 6.1, network-reachable, low complexity, no privileges required, user interaction required, changed scope, with low confidentiality and integrity impact.
Likely exposure
Exposure is most likely in web applications embedding TinyMCE versions before 5.6.0, especially where unauthenticated or low-trust users can save editor content that other users later view.
Exploitation context
The provided bundle reports no KEV listing and gives no cited evidence of active exploitation. Exploitation requires stored content to be viewed by another user, so risk depends heavily on application workflow and trust boundaries.
Researcher notes
The affected-version statement is clear: TinyMCE before 5.6.0. The bundle’s structured affected metadata is sparse, so validate real exposure through dependency and deployment evidence rather than relying only on CPE matching.
Mitigation direction
Upgrade TinyMCE to 5.6.0 or later where affected versions are present.
Check TinyMCE advisory and 5.6 release notes for vendor-specific guidance.
Prioritize internet-facing forms accepting untrusted editor content.
Review server-side content sanitization for stored rich-text submissions.
Inventory bundled or transitive TinyMCE copies in deployed applications.
Validation and detection
Confirm TinyMCE versions in package manifests, lockfiles, and deployed bundles.
Identify routes where untrusted users can save TinyMCE content.
Verify stored editor content is sanitized before later rendering.
Check whether affected content is viewed by administrators or privileged users.
Document whether each application is upgraded, unaffected, or still pending remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.