CVE-2022-23494

Cross-site scripting vulnerability in TinyMCE alerts

Fix

To avoid this vulnerability:

• Upgrade to TinyMCE 5.10.7 or higher for TinyMCE 5.x.
• Upgrade to TinyMCE 6.3.1 or higher for TinyMCE 6.x.

Workaround

To reduce the impact of this vulnerability:

• Ensure the the images_upload_handler returns a valid value as per the images_upload_handler documentation.

References

• https://www.tiny.cloud/docs/release-notes/release-notes5107/#securityfixes
• https://www.tiny.cloud/docs/tinymce/6/6.3-release-notes/#security-fixes

For more information

If you have any questions or comments about this advisory:

• Email us at [email protected]
• Open an issue in the TinyMCE repo

A cross-site scripting (XSS) vulnerability was discovered in the alert and confirm dialogs when these dialogs were provided with malicious HTML content. This can occur in plugins that use the alert or confirm dialogs, such as in the image plugin, which presents these dialogs when certain errors occur. The vulnerability allowed arbitrary JavaScript execution when an alert presented in the TinyMCE UI for the current user.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-23494 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.3.1, 5.10.7); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This vulnerability has been patched in TinyMCE 5.10.7 and TinyMCE 6.3.1 by ensuring HTML sanitization was still performed after unwrapping invalid elements.

1. What is CVE-2022-23494? CVE-2022-23494 is a medium-severity cross-site scripting (XSS) vulnerability in tinymce (npm), affecting versions >= 6.0.0, < 6.3.1. It is fixed in 6.3.1, 5.10.7. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2022-23494? CVE-2022-23494 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-23494?
   • tinymce (npm) (versions >= 6.0.0, < 6.3.1)
   • tinymce/tinymce (composer) (versions >= 6.0.0, < 6.3.1)
   • TinyMCE (nuget) (versions >= 6.0.0, < 6.3.1)
4. Is there a fix for CVE-2022-23494? Yes. CVE-2022-23494 is fixed in 6.3.1, 5.10.7. Upgrade to this version or later.
5. Is CVE-2022-23494 exploitable, and should I be worried? Whether CVE-2022-23494 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-23494 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-23494?
   • Upgrade tinymce to 6.3.1 or later
   • Upgrade tinymce/tinymce to 6.3.1 or later
   • Upgrade TinyMCE to 6.3.1 or later
   • Upgrade tinymce to 5.10.7 or later
   • Upgrade tinymce/tinymce to 5.10.7 or later
   • Upgrade TinyMCE to 5.10.7 or later

Other vulnerabilities in tinymce