dbcve.org
TinymceApplication · Tiny

CVE-2023-45819

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 5.10.8 / 6.7.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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. A cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s Notification Manager API. The vulnerability exploits TinyMCE's unfiltered notification system, which is used in error handling. The conditions for this exploit requires carefully crafted malicious content to have been inserted into the editor and a notification to have been triggered. When a notification was opened, the HTML within the text argument was displayed unfiltered in the notification. The vulnerability allowed arbitrary JavaScript execution when an notification presented in the TinyMCE UI for the current user. This issue could also be exploited by any integration which uses a TinyMCE notification to display unfiltered HTML content. This vulnerability has been patched in TinyMCE 5.10.8 and TinyMCE 6.7.1 by ensuring that the HTML displayed in the notification is sanitized, preventing the exploit. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

Cross-site scripting (XSS) vulnerability in TinyMCE's Notification Manager API allows arbitrary JavaScript execution via unfiltered HTML in notification text. The attack requires malicious content inserted into the editor to trigger a notification, which then renders the HTML unfiltered.

MitigationUpgrade TinyMCE to version 5.10.8 or 6.7.1 or later, which includes HTML sanitization in the notification system. No workarounds exist.

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.10.8>= 6.0.0, < 6.7.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate TinyMCE installation
    Search for tinymce folder, tinymce.min.js, or @tinymce/tinymce-react package in your project dependencies (package.json), node_modules, or static assets directory
    Affected if Cannot locate TinyMCE files means the product is not in use
  2. Identify TinyMCE version
    Check the version field in package.json for npm installations, or open tinymce.min.js and search for 'version:' string to find the version number
    Affected if Version is less than 5.10.8, or greater than or equal to 6.0.0 but less than 6.7.1
  3. Find Notification Manager API usage
    Search your codebase for calls to the Notification Manager API such as editor.notificationManager.open(), editor.notificationManager.msg(), or similar notification methods that display content in the editor
    Affected if Codebase uses the Notification Manager API to display notifications with content that could contain untrusted HTML input

Your environment is affected if TinyMCE version falls within the vulnerable ranges and your application uses the Notification Manager API to render HTML content from untrusted sources.

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.10.8 / 6.7.1 or later
Fixed in 5.10.86.7.1
Interim mitigation

Upgrade TinyMCE to version 5.10.8 or 6.7.1 or later, which includes HTML sanitization in the notification system. No workarounds exist.

Recommended fix High confidence

TinyMCE 5.10.8 (if on 5.x line) or TinyMCE 6.7.1 (if on 6.x line)

  1. Identify your current TinyMCE version by checking your package.json, bower.json, or the tinymce js file
  2. Determine whether you are on the TinyMCE 5.x or 6.x release line
  3. For TinyMCE 5.x users: upgrade to version 5.10.8 or later
  4. For TinyMCE 6.x users: upgrade to version 6.7.1 or later
  5. If using npm: run 'npm install [email protected]' or 'npm install [email protected]' (or latest patch in your major version)
  6. If using a CDN or direct download: replace your tinymce js file with the new version from the official TinyMCE download page
  7. Verify the upgrade by checking that the new version loads correctly in your application
  8. Test that notifications in the editor work as expected with the new version

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

Fix this in Tinymce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45819 — 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-2023-45819 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