dbcve.org
TinymceApplication · Tiny

CVE-2026-47760

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

TinyMCE versions 6.8.0 through 7.0.x contain an XSS vulnerability due to improper SVG namespace scope handling in the built-in sanitizer. Attackers can craft malicious SVG payloads with nested elements to bypass attribute sanitization and execute arbitrary JavaScript in the context of the victim's browser.

MitigationUpgrade TinyMCE to version 7.1.0 or later to obtain the fixed sanitizer. If immediate upgrade is not feasible, implement additional input validation or Content Security Policy headers to mitigate XSS risks until the upgrade can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TinymceApplication
Affected:>= 6.8.0, < 7.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify TinyMCE version
    Access TinyMCE in the browser console and run 'tinymce.majorVersion + "." + tinymce.minorVersion + "." + tinymce.releaseDate' or inspect the tinymce.min.js/tinymce.js file for the version string
    Affected if Version is 6.8.0 through 7.0.x (versions 6.8.0, 6.8.1, 6.8.2, 6.8.3, 6.8.4, 7.0.0, 7.0.1, etc.)
  2. Confirm built-in sanitizer is in use
    Search codebase for imports or usage of 'tinymce.html.Sanitizer' or 'DomParser' with default sanitizer settings
    Affected if Code uses TinyMCE's built-in sanitization (DomParser with default configuration) to process HTML/SVG content
  3. Determine if SVG content from untrusted sources is processed
    Review application code for instances where user-supplied or external SVG data is passed to TinyMCE's editor.setContent(), editor.insertContent(), or similar content insertion methods
    Affected if Untrusted SVG content is being loaded into the TinyMCE editor or processed through its content APIs

You are affected if TinyMCE version is 6.8.0 through 7.0.x AND the built-in sanitizer processes SVG content from untrusted sources such as user uploads, external API data, or pasted content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.1.0 or later
Fixed in 7.1.0
Interim mitigation

Upgrade TinyMCE to version 7.1.0 or later to obtain the fixed sanitizer. If immediate upgrade is not feasible, implement additional input validation or Content Security Policy headers to mitigate XSS risks until the upgrade can be completed.

Recommended fix High confidence

TinyMCE 7.1.0 or later

  1. Check the currently installed TinyMCE version in your project (e.g., via package.json, npm list, or your dependency management system)
  2. Upgrade TinyMCE to version 7.1.0 or later using your package manager (e.g., npm install tinymce@^7.1.0, yarn upgrade tinymce@^7.1.0, or composer update tinymce/tinymce if using PHP)
  3. After upgrading, clear any cached assets and rebuild your application
  4. Verify the new version is correctly installed by checking the TinyMCE version in your application
  5. Test that the editor functions correctly with your existing configuration
Caveat Review the TinyMCE 7.x release notes for potential breaking changes from 6.x before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tinymce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47760 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data