Ckeditor5-Html-Support vulnerabilitiesRanked by how likely they are to be used.
Ckeditor5-Html-Support is made by Ckeditor. We track 1 published vulnerability in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Ckeditor5-Html-Support, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Ckeditor5-Html-Support vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Ckeditor5-Html-Support's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Ckeditor5-Html-Support flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.9%CVE-2022-31175Medium
CKEditor 5 is a JavaScript rich text editor.
Running Ckeditor5-Html-Support? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 `<textarea>` 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.
- Matched to
- Ckeditor5-Html-Support on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1 published vulnerability listed under the name Ckeditor5-Html-Support, across 0 versions.
None of Ckeditor5-Html-Support's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Ckeditor5-Html-Support. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.