# What is CVE-2022-31175? > CVE-2022-31175 is a medium-severity flaw (CVSS 4.7) in Ckeditor5-Html-Embed, published on 3 August 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.9%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-31175 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 20 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 4.7 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.9% (latest exploit-likelihood forecast) - **Published:** 3 August 2022 - **Record last updated:** 9 August 2022 - **Main product:** Ckeditor5-Html-Embed - **Affected products:** 3 ## What is CVE-2022-31175? In plain terms It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### The official description CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5's packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue. ### What kind of flaw is it? - CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Hard: conditions must line up - Login needed first: No login needed - Does someone have to click: Yes, a person has to take an action - What an attacker gets: Can read some data and change some data Severity vector: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N` ## Is CVE-2022-31175 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.9%, 0.9%, 0.9%, 0.9%, 0.9%, 0.9%, 0.9%. ### Timeline - 3 August 2022: Published - 9 August 2022: Record last updated ### How Precursor Intelligence ranks it CVE-2022-31175 scores **20 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2022-31175? The published record lists 3 products. Versions are as published: "before 35.0.1" means every version up to, but not including, 35.0.1. - [Ckeditor5-Html-Embed](https://www.precursorintelligence.com/product/ckeditor/ckeditor5-html-embed) by [Ckeditor](https://www.precursorintelligence.com/vendors/ckeditor) (Application): before 35.0.1 - [Ckeditor5-Html-Support](https://www.precursorintelligence.com/product/ckeditor/ckeditor5-html-support) by [Ckeditor](https://www.precursorintelligence.com/vendors/ckeditor) (Application): before 35.0.1 - [Ckeditor5-Markdown-Gfm](https://www.precursorintelligence.com/product/ckeditor/ckeditor5-markdown-gfm) by [Ckeditor](https://www.precursorintelligence.com/vendors/ckeditor) (Application): before 35.0.1 ## How do I fix CVE-2022-31175? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [ckeditor.com](https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html) (Vendor advisory) - [ckeditor.com](https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html) (Vendor advisory) - [ckeditor.com](https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html) (Vendor advisory) - [github.com](https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j) (Third-party advisory) ## Questions ### What is CVE-2022-31175? CVE-2022-31175 is a medium-severity flaw in Ckeditor5-Html-Embed, published on 3 August 2022. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### How serious is CVE-2022-31175? It scores 4.7 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-31175 is 20 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2022-31175 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2022-31175 affect? For Ckeditor5-Html-Embed: before 35.0.1. The record lists 3 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2022-31175? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2022-31175 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact