Cross-Site Scripting (XSS) in ckeditor4 (CVE-2021-41165)
Summary
Cross-site scripting in ckeditor4 (CVE-2021-41165). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.17.0 or later.
Original description
The description as published by the source.
CKEditor4 is an open source WYSIWYG HTML editor. In affected version a vulnerability has been discovered in the core HTML processing module and may affect all plugins used by CKEditor 4. The vulnerability allowed to inject malformed comments HTML bypassing content sanitization, which could result in executing JavaScript code. It affects all users using the CKEditor 4 at version < 4.17.0. The problem has been recognized and patched. The fix will be available in version 4.17.0.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-41165 has been found in ckeditor4.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ckeditor4 to 4.17.0 or later.
If unsure, ask your IT team or search "ckeditor4 CVE-2021-41165" on the vendor's site.
CVE-2021-41165 (ckeditor4) — CWE-79
Attack vector: remote (network-reachable)
Patched: 4.17.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in ckeditor4.
Check the vendor advisory for the affected versions of ckeditor4.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.17.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ckeditor4' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ckeditor4' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ckeditor4を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ckeditor4 to 4.17.0ステージング環境で 4.17.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2021-41165 ckeditor
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory drupal.org
- package github.com
- patch oracle.com
- patch oracle.com
- web oracle.com