Loading...
Skip to main content

CVE-2023-45819 — TinyMCE XSS vulnerability in TinyMCE — CVE Details

MEDIUM

TinyMCE XSS vulnerability in notificationManager.open API

Published October 19, 2023Updated February 16, 2024Source: osv

Summary

### Impact A [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/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/#securityfixes> * <https://tiny.cloud/docs/tinymce/6/6.7.1-release-notes/#security-fixes> ### For more information If you have any questions or comments about this advisory: * Email us at <infosec@tiny.cloud> * Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)

Advisory Timeline

  • First published October 19, 2023 (1089 days ago).
  • Last revised February 16, 2024 — 120 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

NuGet
Update TinyMCE to 5.10.8 or later
dotnet add package TinyMCE --version 5.10.8
npm
Update tinymce to 6.7.1 or later
npm install tinymce@6.7.1
NuGet
Update TinyMCE to 6.7.1 or later
dotnet add package TinyMCE --version 6.7.1
Composer
Update tinymce/tinymce to 5.10.8 or later
composer require "tinymce/tinymce:^5.10.8"
Composer
Update tinymce/tinymce to 6.7.1 or later
composer require "tinymce/tinymce:^6.7.1"
npm
Update tinymce to 5.10.8 or later
npm install tinymce@5.10.8

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (6)

Affects 3 ecosystems: npm (1), nuget (1), packagist (1).

PackageEcosystemAffectedFixed In
TinyMCE
nuget
3.4.3.2, 3.4.4, 3.4.5, 3.4.7 (+176 more)5.10.8
tinymce
npm
All versions6.7.1
TinyMCE
nuget
6.0.0, 6.0.1, 6.0.2, 6.0.3 (+14 more)6.7.1
tinymce/tinymce
packagist
4.0.0, 4.0.1, 4.0.10, 4.0.11 (+167 more)5.10.8
tinymce/tinymce
packagist
6.0.0, 6.0.1, 6.0.2, 6.0.3 (+16 more)6.7.1
tinymce
npm
All versions5.10.8

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-79
    Cross-site Scripting (XSS)MITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 6.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
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

Frequently Asked Questions

What is CVE-2023-45819?
TinyMCE XSS vulnerability in notificationManager.open API This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 6.1/10).
How do I check if my project is affected by CVE-2023-45819?
CVE-2023-45819 affects TinyMCE, tinymce and tinymce/tinymce. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2023-45819 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
6.1

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-hgqx-r2hp-jr38

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies