Cross-site Scripting in CKEditor4GHSA-f6rf-9m92-x2hh
Fix: ckeditor/ckeditor4@d158413GHSA-f6rf-9m92-x2hh is a Cross-site Scripting (XSS) vulnerability in drupal. A fix is available for drupal — see the affected versions and patch details below.
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 GHSA-f6rf-9m92-x2hh.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
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.
ckeditor4npmDescription
CKEditor4 is an open source what-you-see-is-what-you-get HTML editor. A vulnerability has been discovered in the core HTML processing module and may affect all plugins used by CKEditor 4 prior to version 4.18.0. The vulnerability allows someone to inject malformed HTML bypassing content sanitization, which could result in executing JavaScript code. This problem has been patched in version 4.18.0. There are currently no known workarounds.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Bitnami | drupal | ≥ 8.0.0&&< 9.2.15 | 9.2.15 |
Affected Products
ckeditorckeditordrupaldrupalfedorafedoraprojectapplication expressoraclecommerce merchandisingoraclefinancial services analytical applications infrastructureoracleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal to 9.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6rf-9m92-x2hh is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-f6rf-9m92-x2hh in your dependencies?
Find it across Bitnami, including transitive dependencies.