CVE-2022-48110
Description
CKSource CKEditor 5 35.4.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the Full Featured CKEditor5 widget. NOTE: the vendor's position is that this is not a vulnerability. The CKEditor 5 documentation discusses that it is the responsibility of an integrator (who is adding CKEditor 5 functionality to a website) to choose the correct security settings for their use case. Also, safe default values are established (e.g., config.htmlEmbed.showPreviews is false).
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
CKEditor 5 35.4.0's Full Featured widget can be misconfigured to enable stored XSS via the HTML embed feature, but the vendor considers this an integrator responsibility.
Vulnerability
Overview CVE-2022-48110 describes a potential cross-site scripting (XSS) risk in CKEditor 5 version 35.4.0 when using the Full Featured configuration. The issue arises from the HTML embed feature, which allows editors to insert arbitrary HTML snippets, including `` tags, into content [1]. Unlike other features that enforce content filtering, the HTML embed feature is designed to bypass CKEditor 5's built-in filtering mechanisms, making it a powerful tool for advanced users [1].
Exploitation
Context Exploitation requires an integrator to enable the HTML embed feature and configure it with unsafe settings. Specifically, if config.htmlEmbed.showPreviews is set to true, a preview of the embedded HTML is rendered, including potentially malicious scripts [3]. An attacker with edit access could then inject HTML containing JavaScript. The attack vector is stored—the malicious payload persists in the editor content and executes when a viewer (e.g., an administrator) loads a preview or the published content [1].
Impact and
Vendor Position If exploited, an attacker could execute arbitrary JavaScript in the context of the user viewing the content, leading to session hijacking, data theft, or defacement. The vendor, CKSource, maintains that this is not a vulnerability in CKEditor 5 itself, but rather a consequence of integrator choices [3]. The documentation explicitly states that integrators must select security settings appropriate for their use case, and the default setting (showPreviews: false) is safe [1][3].
Mitigation
No patch is required from CKEditor 5 as version 35.4.0 is not affected by a code defect; the risk is entirely configurational. Integrators should ensure config.htmlEmbed.showPreviews remains false unless they have explicitly trusted all editors and implemented additional server-side sanitization [1][3]. Reviewing the HTML embed feature's security implications is advised before enabling it in any production environment [2].
AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
ckeditor5npm | < 36.0.0 | 36.0.0 |
Affected products
2- CKSource/CKEditor 5description
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4News mentions
0No linked articles in our index yet.