What is the CVSS score of CVE-2026-47760?

CVE-2026-47760 has a CVSS 3.1 base score of 8.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of TinyMCE are affected by CVE-2026-47760?

Any organization using TinyMCE rich-text editor versions 6.8.0 through 7.0.x faces elevated risk of user account compromise and data theft.. A patch is available.

How to fix or mitigate CVE-2026-47760?

Within 24 hours: Inventory all applications using TinyMCE versions 6.8.0-7.0.x and classify by user exposure (customer-facing, internal, admin-only). Within 7 days: Monitor the TinyMCE project for patch release timeline; assess feasibility of reverting to versions before 6.8.0. Within 30 days: Apply patch immediately upon release or implement compensating controls; conduct security testing before production deployment.

TinyMCE CVE-2026-47760

EUVD-2026-32920 HIGH

Cross-site Scripting (XSS) (CWE-79)

2026-05-28 GitHub_M

GHSA-mh5m-5hw4-5c69

XSS Tinymce

8.7

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.7 HIGH

AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch available

May 28, 2026 - 17:01 EUVD

Analysis Generated

May 28, 2026 - 15:51 vuln.today

DescriptionGitHub Advisory

TinyMCE is an open source rich text editor. From 6.8.0 to before 7.1.0, TinyMCE contains an XSS vulnerability caused by improper SVG namespace scope handling in the sanitizer. A crafted payload using nested elements can bypass attribute sanitization and execute arbitrary JavaScript. This vulnerability is fixed in 7.1.0.

AnalysisAI

Stored/reflected cross-site scripting in TinyMCE rich text editor versions 6.8.0 through 7.0.x allows authenticated users to inject and execute arbitrary JavaScript in the context of any application embedding the editor. The flaw stems from improper SVG namespace scope handling in the built-in sanitizer, letting nested-element payloads bypass attribute sanitization. No public exploit identified at time of analysis, but the issue is disclosed via a GitHub security advisory with a CVSS of 8.7 reflecting scope change to the embedding application.

Technical ContextAI

TinyMCE is a widely deployed WYSIWYG editor (cpe:2.3:a:tinymce:tinymce) embedded in CMSes, SaaS dashboards, ticketing systems, and email composers. The vulnerability is a CWE-79 (Improper Neutralization of Input During Web Page Generation) caused by namespace confusion when the sanitizer processes SVG subtrees: SVG allows XML namespaces and foreignObject content where HTML parsing rules differ from the surrounding document, and when nested elements cross these boundaries the attribute allow/deny logic does not re-evaluate scope correctly. As a result, event handler attributes (e.g., onload, onerror) or javascript: URIs on otherwise-stripped elements survive sanitization and are interpreted by the browser when the content is later rendered.

RemediationAI

Vendor-released patch: TinyMCE 7.1.0 - upgrade all embedded instances to 7.1.0 or later as published in the upstream advisory at https://github.com/tinymce/tinymce/security/advisories/GHSA-mh5m-5hw4-5c69. Where an immediate upgrade is not possible, apply a server-side secondary sanitization pass on TinyMCE output using a hardened sanitizer (e.g., DOMPurify with SVG and MathML namespaces locked down) before persisting or rendering content, accepting that this may strip legitimate SVG markup users have authored; alternatively configure TinyMCE's valid_elements / invalid_elements to deny svg, foreignObject, and event-handler attributes, at the cost of losing inline SVG editing. Enforce a strict Content Security Policy (script-src without 'unsafe-inline' and with no permissive nonces echoed into editor output) to blunt the impact of any sanitizer bypass, noting CSP will not prevent same-origin DOM manipulation if inline scripts are otherwise permitted on the page.