How severe is CVE-2022-23494?

CVE-2022-23494 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-23494?

CVE-2022-23494 affects the following packages: tinymce (npm), tinymce (npm), TinyMCE (NuGet), TinyMCE (NuGet), tinymce/tinymce (Packagist), tinymce/tinymce (Packagist). Ecosystems affected: npm, NuGet, Packagist.

How do I fix CVE-2022-23494?

Update tinymce to 6.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23494 is resolved across your whole dependency graph.

How do I detect CVE-2022-23494 in my npm, NuGet, Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tinymce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2022-23494 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-23494?

O3 pinpoints whether CVE-2022-23494 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2022-23494 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-23494 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-23494?

CVE-2022-23494 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-23494?

CVE-2022-23494 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-23494 published, and has it been updated?

CVE-2022-23494 was published on December 8, 2022 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm.NET NuGet🐘 Packagist

CVE-2022-23494

MEDIUM

Cross-site scripting vulnerability in TinyMCE alerts

Also known asGHSA-gg8r-xjwq-4w92

Published

Dec 8, 2022

Updated

Apr 10, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk56th percentile-0.91%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

tinymcenpm

1.1Mdownloads / week

Description

tinymce is an open source rich text editor. 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. 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. Users are advised to upgrade to either 5.10.7 or 6.3.1. Users unable to upgrade may ensure the the images_upload_handler returns a valid value as per the images_upload_handler documentation.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`tinymce`	≥ 6.0.0&&< 6.3.1	6.3.1
📦npm	`tinymce`	all versions	5.10.7
.NETNuGet	`TinyMCE`	≥ 6.0.0&&< 6.3.1	6.3.1
.NETNuGet	`TinyMCE`	all versions	5.10.7
🐘Packagist	`tinymce/tinymce`	≥ 6.0.0&&< 6.3.1	6.3.1
🐘Packagist	`tinymce/tinymce`	all versions	5.10.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tinymce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update tinymce to 6.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23494 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-23494 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-23494. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

tinymce is an open source rich text editor. 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. This vulnerability has been patched in TinyMCE 5.10.7 and TinyMCE 6.3.1 by ensuring HTML sanitization was still performed after un

O3 Security · Impact-Aware SCA

Is CVE-2022-23494 in your dependencies?

O3 detects CVE-2022-23494 across npm, NuGet, Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works