Quick answers
- Is CVE-2020-9281 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-9281 being exploited in the wild.
- How severe is CVE-2020-9281?
- Low severity, with a CVSS score of 3.1, published 7 May 2021.
- Which products and versions are affected?
- CKEditor 4 before 4.14.0; ckeditor4 (npm) SEMVER:introduced=0,fixed=4.14.0.
- Is there a fix for CVE-2020-9281?
- Yes. ckeditor4 (npm): upgrade to 4.14.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-9281 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2020-9281?
- Check whether you run CKEditor 4 or 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.14.0 or later
npm install ckeditor4@4.14.0
Technical details
This is a cross-site scripting (XSS) vulnerability (CWE-79) in CKEditor 4's HTML Data Processor component. The vulnerability exists in versions before 4.14.0 and is triggered when processing specially crafted "protected" comments using the cke_protected syntax. An attacker can inject arbitrary JavaScript code that will execute in the context of the user's browser with access to the same origin. The attack requires user interaction (the user must load a document containing the malicious payload), but does not require authentication. The vulnerability was patched in version 4.14.0.
Affected products
- CKEditor CKEditor 4 before 4.14.0
Identifiers
- CVE-2020-9281
- GHSA-vcjf-mgcg-jxjq
Timeline
- 2020-03-07: disclosed: Initial disclosure on NVD
- 2020: patched: Fixed in CKEditor 4.14.0
- 2021-05-07: advisory: GHSA-vcjf-mgcg-jxjq published