CVE-2025-58064
Fix: ckeditor/ckeditor5@b210e90CVE-2025-58064 is a Cross-site Scripting (XSS) vulnerability in ckeditor5. O3 Security confirms whether CVE-2025-58064 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CKEditor is susceptible to Cross-Site Scripting (XSS) through its clipboard package
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
ckeditor5npm@ckeditor/ckeditor5-clipboardnpmDescription
CKEditor 5 is a modern JavaScript rich-text editor with an MVC architecture. ckeditor5 and ckeditor5-clipboard versions 46.0.0 through 46.0.2 and 44.2.0 through 45.2.1 contain a Cross-Site Scripting (XSS) vulnerability. Ability to exploit could be triggered by a specific user action (leading to unauthorized JavaScript code execution) if the attacker managed to insert a malicious content into the editor, which might happen with a very specific editor configuration. This vulnerability affects installations where the editor configuration meets one of the following criteria: the HTML embed plugin is enabled, or there is a custom plugin introducing an editable element where view RawElement is enabled. This issue is fixed in versions 45.2.2 and 46.0.3 of both ckeditor5 and ckeditor5-clipboard.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ckeditor5 | ≥ 46.0.0&&< 46.0.3 | 46.0.3 |
| 📦npm | @ckeditor/ckeditor5-clipboard | ≥ 44.2.0&&< 45.2.2 | 45.2.2 |
| 📦npm | ckeditor5 | ≥ 44.2.0&&< 45.2.2 | 45.2.2 |
| 📦npm | @ckeditor/ckeditor5-clipboard | ≥ 46.0.0&&< 46.0.3 | 46.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckeditor5. 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 ckeditor5 to 46.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58064 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-2025-58064 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-2025-58064. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-58064 in your dependencies?
O3 detects CVE-2025-58064 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.