GHSA-rgx6-rjj4-c388
MEDIUMGHSA-rgx6-rjj4-c388 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in ckeditor4. O3 Security confirms whether GHSA-rgx6-rjj4-c388 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
ckeditor4 vulnerable to cross-site scripting
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
A cross-site scripting (XSS) vulnerability in the HTML Data Processor in CKEditor 4 4.14.0 through 4.16.x before 4.16.1 allows remote attackers to inject executable JavaScript code through a crafted comment because --!> is mishandled.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ckeditor4 | ≥ 4.14.0&&< 4.16.1 | 4.16.1 |
| 🐘Packagist | drupal/core | ≥ 7.0.0&&< 7.80 | 7.80 |
| 🐘Packagist | drupal/core | ≥ 8.0.0&&< 8.9.16 | 8.9.16 |
| 🐘Packagist | drupal/core | ≥ 9.0.0&&< 9.0.14 | 9.0.14 |
| 🐘Packagist | drupal/core | ≥ 9.1.0&&< 9.1.9 | 9.1.9 |
| 🐘Packagist | drupal/drupal | ≥ 7.0.0&&< 7.80 | 7.80 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckeditor4. 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 ckeditor4 to 4.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rgx6-rjj4-c388 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 GHSA-rgx6-rjj4-c388 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 GHSA-rgx6-rjj4-c388. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is GHSA-rgx6-rjj4-c388 in your dependencies?
O3 detects GHSA-rgx6-rjj4-c388 across npm, Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.