Quick answers
- Is CVE-2021-41164 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2021-41164 being exploited in the wild.
- How severe is CVE-2021-41164?
- Low severity, with a CVSS score of 3.1, published 17 November 2021.
- Which products and versions are affected?
- ckeditor4 (npm) SEMVER:introduced=0,fixed=4.17.0.
- Is there a fix for CVE-2021-41164?
- Yes. ckeditor4 (npm): upgrade to 4.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2021-41164 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2021-41164?
- Check whether you run ckeditor4 (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ckeditor4 (npm): upgrade to 4.17.0 or later
npm install ckeditor4@4.17.0
Technical details
The vulnerability is a cross-site scripting (XSS) flaw in CKEditor 4's Advanced Content Filter module (CWE-79). The root cause is insufficient validation of malformed HTML input, allowing attackers to bypass the sanitization logic designed to prevent script injection. An attacker with the ability to provide content to the editor (typically authenticated users or those with content-upload privileges) can craft malicious HTML that, when processed by ACF, is not properly sanitized and results in JavaScript execution in the context of the user's browser. The vulnerability affects all versions of CKEditor 4 prior to 4.17.0, and is patched in version 4.17.0 and later.
Affected products
- CKSource CKEditor 4 < 4.17.0
Identifiers
- CVE-2021-41164
- GHSA-pvmx-g8h5-cprj
Timeline
- 2021-11-17: disclosed
- 2021-11-17: patched: Patched in version 4.17.0