Quick answers
- Is CVE-2022-0350 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-0350 being exploited in the wild.
- How severe is CVE-2022-0350?
- Low severity, with a CVSS score of 3.1, published 1 April 2022.
- Which products and versions are affected?
- vditor (npm) SEMVER:introduced=0,fixed=3.8.13.
- Is there a fix for CVE-2022-0350?
- Yes. vditor (npm): upgrade to 3.8.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-0350 attacked?
- It is attacked over the network.
- Am I affected by CVE-2022-0350?
- Check whether you run vditor (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
- vditor (npm): upgrade to 3.8.13 or later
npm install vditor@3.8.13
Technical details
This is a stored cross-site scripting vulnerability (CWE-79) in vditor prior to version 3.8.13. The vulnerability exists in the editor's handling of user-supplied input, allowing authenticated users to inject malicious JavaScript code that is stored and later executed when other users view the content. The attack requires user interaction (someone viewing the malicious content) and authenticated access to inject the payload. An attacker can steal session tokens, perform actions on behalf of other users, or capture sensitive data. The fix was released in version 3.8.13 as evidenced by commit e912e36ea98251d700499b1ac7702708d3398476.
Affected products
- Vanessa219 vditor prior to 3.8.13
Identifiers
- CVE-2022-0350
- GHSA-689x-x68p-fph3
Timeline
- 2022-03-31: disclosed: NVD published
- 2022-04-01: advisory: GitHub Security Advisory GHSA-689x-x68p-fph3 published
- 2022-04-08: patched: Fix released in version 3.8.13