CVE-2022-31175: CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5's packages i...

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 `<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.

Metrics

CVSS 3.1

4.7/10

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS Probability

0.58%

43.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-79

Affected Software

Vendor	Product	Versions
Ckeditor	Ckeditor5-Html-Embed	< 35.0.1
Ckeditor	Ckeditor5-Html-Support	< 35.0.1
Ckeditor	Ckeditor5-Markdown-Gfm	< 35.0.1

References

https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.htmlVendor Advisory
https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.htmlVendor Advisory
https://ckeditor.com/docs/ckeditor5/latest/features/markdown.htmlVendor Advisory
https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6jThird Party Advisory
https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.htmlVendor Advisory
https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.htmlVendor Advisory
https://ckeditor.com/docs/ckeditor5/latest/features/markdown.htmlVendor Advisory
https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6jThird Party Advisory

Timeline

Published: Aug 3, 2022
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2022-31175?

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.

How severe is CVE-2022-31175?

CVE-2022-31175 has a CVSS score of 4.7/10 (MEDIUM severity). The EPSS model estimates a 0.58% probability of exploitation in the next 30 days.

How do I fix CVE-2022-31175?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.