dbcve.org
TinymceApplication · Tiny

CVE-2026-47762

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 5.11.1 / 7.9.3 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. Prior to 5.11.1, 7.9.3, and 8.5.1, there is a stored XSS vulnerability via forged mce:protected comments. Allows attackers to bypass sanitization and inject scripts that execute when content is restored. Impacts users who utilize the protect option. This vulnerability is fixed in 5.11.1, 7.9.3, and 8.5.1.

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 contains a stored XSS vulnerability where attackers can forge mce:protected comments to bypass sanitization and inject malicious scripts. These scripts execute when content is restored in the editor, specifically impacting users who utilize TinyMCE's protect option.

MitigationUpgrade TinyMCE to version 5.11.1, 7.9.3, or 8.5.1 or later. If immediate upgrading is not possible, avoid using the protect option or implement additional output sanitization on content before rendering.

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:< 5.11.1>= 6.0.0, < 7.9.3>= 8.0.0, < 8.5.1

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
    Locate the tinymce.js or tinymce.min.js file in your project, or check package.json for the tinymce dependency version. Open the JS file and search for a version string (e.g., 'version:"7.9.0"' or similar).
    Affected if The installed version is less than 5.11.1, or between 6.0.0 and 7.9.2 inclusive, or between 8.0.0 and 8.5.0 inclusive.
  2. Locate TinyMCE configuration
    Search your codebase for tinymce.init() calls or TinyMCE configuration files. Look for the 'protect' option within the configuration object.
    Affected if The protect option is present and configured in your TinyMCE settings.
  3. Inspect protect option usage
    In your TinyMCE configuration, examine the protect setting. It is typically an array of regular expressions used to protect content from being stripped during sanitization. Check if any patterns are defined that could be exploited.
    Affected if The protect option contains user-controlled or overly permissive regex patterns that could allow injection of mce:protected comments.
  4. Examine stored content for mce:protected comments
    If you have access to the database or content storage where TinyMCE content is saved, search for any content containing the string 'mce:protected'. Inspect these entries for suspicious patterns.
    Affected if Stored content contains mce:protected comments that were not intentionally added by your application.

You are affected if your TinyMCE version falls within the vulnerable ranges AND the protect option is enabled in your configuration, allowing attackers to inject forged mce:protected comments.

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 5.11.1 / 7.9.3 / 8.5.1 or later
Fixed in 5.11.17.9.38.5.1
Interim mitigation

Upgrade TinyMCE to version 5.11.1, 7.9.3, or 8.5.1 or later. If immediate upgrading is not possible, avoid using the protect option or implement additional output sanitization on content before rendering.

Recommended fix High confidence

Upgrade to 5.11.1 (for 5.x users), 7.9.3 (for 6.x-7.x users), or 8.5.1 (for 8.x users)

  1. Identify your current TinyMCE version by checking your package.json, dependency files, or the tinymce script version
  2. If using TinyMCE 5.x (versions < 5.11.1): upgrade to version 5.11.1
  3. If using TinyMCE 6.x or 7.x (versions >= 6.0.0, < 7.9.3): upgrade to version 7.9.3
  4. If using TinyMCE 8.x (versions >= 8.0.0, < 8.5.1): upgrade to version 8.5.1
  5. Update your package manager dependency (e.g., npm install [email protected], [email protected], or [email protected])
  6. Clear any cached browser assets and rebuild your application
  7. Test that the editor loads correctly and the protect option functions as expected
Caveat Minimal risk; these are patch releases fixing a security vulnerability with no breaking changes expected for normal editor usage

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-47762 — 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-47762 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