Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1amended

TinyMCE XSS vulnerability in notificationManager.open API

CVE-2023-45819GHSA-hgqx-r2hp-jr38

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tinymce 6.7.1, 5.10.8; tinymce/tinymce 6.7.1, 5.10.8; tinymce 6.7.1, 5.10.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • NuGet tinymce

    Affected
    >= 6.0.0, < 6.7.1< 5.10.8
    Fixed in
    5.10.8, 6.7.1

  • Packagist tinymce/tinymce

    Affected
    >= 6.0.0, < 6.7.1< 5.10.8
    Fixed in
    5.10.8, 6.7.1

  • npm tinymce

    Affected
    >= 6.0.0, < 6.7.1< 5.10.8
    Fixed in
    5.10.8, 6.7.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2023-45819: 0.63% estimated exploitation activity in the next 30 days; percentile 50.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-hgqx-r2hp-jr38

  2. Revision 1 · created ·

    Published from osv record GHSA-hgqx-r2hp-jr38

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-45819

Advisory: TinyMCE XSS vulnerability in notificationManager.open API
IDs: CVE-2023-45819, GHSA-hgqx-r2hp-jr38
Record: https://patchnext.com/advisories/cve-2023-45819 (revision 2, source checked 26 Oct 2026, 12:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tinymce 6.7.1, 5.10.8; tinymce/tinymce 6.7.1, 5.10.8; tinymce 6.7.1, 5.10.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet tinymce: affected >= 6.0.0, < 6.7.1; < 5.10.8; fixed in 5.10.8, 6.7.1
- Packagist tinymce/tinymce: affected >= 6.0.0, < 6.7.1; < 5.10.8; fixed in 5.10.8, 6.7.1
- npm tinymce: affected >= 6.0.0, < 6.7.1; < 5.10.8; fixed in 5.10.8, 6.7.1

## Suggested inspection (read-only)
- NuGet tinymce: check the installed version with your package manager.
- Packagist tinymce/tinymce: check the installed version with your package manager.
- `npm ls tinymce --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tinymce, tinymce/tinymce.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hgqx-r2hp-jr38 (OSV record GHSA-hgqx-r2hp-jr38 lists affected ranges: npm tinymce >=6.0.0 =0 =6.0.0 =0 =6.0.0 =0 <5.10.8 (fixed))
- Verified: https://github.com/advisories/GHSA-hgqx-r2hp-jr38 (GitHub-reviewed advisory GHSA-hgqx-r2hp-jr38 lists affected ranges: npm tinymce >=6.0.0 =0 =6.0.0 =0 =6.0.0 =0 <5.10.8)

Commands are suggestions: review each one before running it.

Loading voting…