CVE-2025-58064 — ckeditor5
Fix: ckeditor/ckeditor5@b210e90CVE-2025-58064 is a Cross-site Scripting (XSS) vulnerability in ckeditor5. A fix is available for ckeditor5 — see the affected versions and patch details below.
CKEditor is susceptible to Cross-Site Scripting (XSS) through its clipboard package
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-58064.
EPSS Exploitation Probability
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.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
ckeditor5npm@ckeditor/ckeditor5-clipboardnpmDescription
Impact
A Cross-Site Scripting (XSS) vulnerability has been discovered in the CKEditor 5 clipboard package. This vulnerability 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 only installations where the editor configuration meets one of the following criteria:
- HTML embed plugin is enabled
- Custom plugin introducing editable element which implements view
RawElementis enabled
Patches
The problem has been recognized and patched. The fix will be available in version 46.0.3 (and above), and explicitly in version 45.2.2.
For more information
Email us at [email protected] if you have any questions or comments about this advisory.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ckeditor5 | ≥ 46.0.0&&< 46.0.3 | 46.0.3npm install ckeditor5@46.0.3 |
| 📦npm | @ckeditor/ckeditor5-clipboard | ≥ 44.2.0&&< 45.2.2 | 45.2.2npm install @ckeditor/ckeditor5-clipboard@45.2.2 |
| 📦npm | ckeditor5 | ≥ 44.2.0&&< 45.2.2 | 45.2.2npm install ckeditor5@45.2.2 |
| 📦npm | @ckeditor/ckeditor5-clipboard | ≥ 46.0.0&&< 46.0.3 | 46.0.3npm install @ckeditor/ckeditor5-clipboard@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-58064 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2025-58064 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.