CVE-2026-47762
Stored XSS in TinyMCE Rich Text Editor
Publication date: 2026-05-28
Last updated on: 2026-05-28
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tinymce | tinymce | to 5.11.1 (exc) |
| tinymce | tinymce | to 7.9.3 (exc) |
| tinymce | tinymce | to 8.5.1 (exc) |
| tinymce | tinymce | From 6.0.0 (inc) to 6.8.6 (inc) |
| tinymce | tinymce | From 7.0.0 (inc) to 7.9.3 (exc) |
| tinymce | tinymce | From 8.0.0 (inc) to 8.5.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, users should upgrade TinyMCE to the patched versions 5.11.1, 7.9.3, or 8.5.1, which include fixes that validate decoded `mce:protected` content against configured protect regex rules before restoration.
There is no official workaround available, so upgrading to the fixed versions is the recommended immediate step.
Can you explain this vulnerability to me?
This vulnerability is a stored Cross-Site Scripting (XSS) issue in TinyMCE, an open source rich text editor. It occurs in versions before 5.11.1, 7.9.3, and 8.5.1 and allows attackers to bypass sanitization by using forged mce:protected comments.
Attackers can inject malicious scripts that execute when the content is restored, impacting users who utilize the protect option in TinyMCE.
The vulnerability is fixed by validating decoded mce:protected content against configured protect regex rules before restoration.
How can this vulnerability impact me? :
This vulnerability can have a significant impact by allowing attackers to execute malicious scripts in the context of the affected application.
- It can lead to unauthorized access to sensitive information (confidentiality impact).
- It can compromise data integrity by allowing attackers to manipulate content.
- The vulnerability has a high severity rating with a CVSS score of 8.7, indicating a serious risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability is a stored cross-site scripting (XSS) issue that allows attackers to inject malicious scripts, potentially compromising the confidentiality and integrity of data handled by TinyMCE.
Such a compromise could impact compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and data breaches.
By allowing script injection and execution, this vulnerability could lead to unauthorized data exposure or manipulation, thereby violating these regulatory requirements.
Mitigation requires upgrading to patched versions of TinyMCE (5.11.1, 7.9.3, or 8.5.1) to prevent exploitation and help maintain compliance.