vulnerability / NVI-00005640 / Revision 3
TinyMCE XSS vulnerability in notificationManager.open API
OSV carries this publisher advisory for tinymce, TinyMCE, tinymce/tinymce, tinymce, TinyMCE. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
6.1 MEDIUM (3.1)
security-advisories@github.com severity; no combined Null risk score.
6.1 MEDIUM (3.1)
nvd@nist.gov severity; no combined Null risk score.
0.634%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.50369. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
tinymce
source listedSEMVER: introduced 6.0.0; fixed 6.7.1
### Impact 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. ### Patches 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. ### Fix To avoid this vulnerability: * Upgrade to TinyMCE 5.10.8 or higher for TinyMCE 5.x. * Upgrade to TinyMCE 6.7.1 or higher for TinyMCE 6.x. ### References * <https://tiny.cloud/docs/release-notes/release-notes5108/#securityfixe
TinyMCE
source listedECOSYSTEM: introduced 6.0.0; fixed 6.7.1
### Impact 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. ### Patches 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. ### Fix To avoid this vulnerability: * Upgrade to TinyMCE 5.10.8 or higher for TinyMCE 5.x. * Upgrade to TinyMCE 6.7.1 or higher for TinyMCE 6.x. ### References * <https://tiny.cloud/docs/release-notes/release-notes5108/#securityfixe
tinymce/tinymce
source listedECOSYSTEM: introduced 6.0.0; fixed 6.7.1
### Impact 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. ### Patches 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. ### Fix To avoid this vulnerability: * Upgrade to TinyMCE 5.10.8 or higher for TinyMCE 5.x. * Upgrade to TinyMCE 6.7.1 or higher for TinyMCE 6.x. ### References * <https://tiny.cloud/docs/release-notes/release-notes5108/#securityfixe
tinymce
source listedSEMVER: introduced 0; fixed 5.10.8
### Impact 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. ### Patches 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. ### Fix To avoid this vulnerability: * Upgrade to TinyMCE 5.10.8 or higher for TinyMCE 5.x. * Upgrade to TinyMCE 6.7.1 or higher for TinyMCE 6.x. ### References * <https://tiny.cloud/docs/release-notes/release-notes5108/#securityfixe
TinyMCE
source listedECOSYSTEM: introduced 0; fixed 5.10.8
### Impact 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. ### Patches 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. ### Fix To avoid this vulnerability: * Upgrade to TinyMCE 5.10.8 or higher for TinyMCE 5.x. * Upgrade to TinyMCE 6.7.1 or higher for TinyMCE 6.x. ### References * <https://tiny.cloud/docs/release-notes/release-notes5108/#securityfixe
tinymce/tinymce
source listedECOSYSTEM: introduced 0; fixed 5.10.8
### Impact 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. ### Patches 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. ### Fix To avoid this vulnerability: * Upgrade to TinyMCE 5.10.8 or higher for TinyMCE 5.x. * Upgrade to TinyMCE 6.7.1 or higher for TinyMCE 6.x. ### References * <https://tiny.cloud/docs/release-notes/release-notes5108/#securityfixe
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 6.7.1 for tinymce. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 6.7.1 for tinymce/tinymce. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 5.10.8 for tinymce. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 5.10.8 for tinymce/tinymce. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
- NVD lastModified does not establish freshness of every associated CPE record.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-hgqx-r2hp-jr38 ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
- CVE-2023-45819 ↗
NIST National Vulnerability Database · official catalog
Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.
- CVE-2023-45819 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 3 ·
Source facts changed; compare the preserved prior revision.
- Revision 2 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.