How severe is CVE-2024-45613?

No CVSS score has been assigned to CVE-2024-45613 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-45613?

CVE-2024-45613 affects the following packages: ckeditor5 (npm), @ckeditor/ckeditor5-clipboard (npm). Ecosystems affected: npm.

How do I fix CVE-2024-45613?

Update ckeditor5 to 43.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45613 is resolved across your whole dependency graph.

How do I detect CVE-2024-45613 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckeditor5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-45613 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2024-45613 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-45613 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-45613?

CVE-2024-45613 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-45613?

CVE-2024-45613 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-45613 published, and has it been updated?

CVE-2024-45613 was published on September 25, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2024-45613 — ckeditor5

CVE-2024-45613 is a Cross-site Scripting (XSS) vulnerability in ckeditor5. A fix is available for ckeditor5 — see the affected versions and patch details below.

CKEditor 5 has Cross-site Scripting vulnerability in the clipboard package

Also known asGHSA-rgg8-g5x8-wr9v

Published

Sep 25, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-45613.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

269other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

ckeditor5npm

1.3Mdownloads / week

@ckeditor/ckeditor5-clipboardnpm

1.2Mdownloads / week

Description

Impact

During a recent internal audit, we identified a Cross-Site Scripting (XSS) vulnerability in the CKEditor 5 clipboard package. This vulnerability could be triggered by a specific user action, leading to unauthorized JavaScript code execution, if the attacker managed to insert a malicious content into the editor, which might happen with a very specific editor configuration.

This vulnerability affects only installations where the editor configuration meets the following criteria:

The Block Toolbar plugin is enabled.
One of the following plugins is also enabled:
- General HTML Support with a configuration that permits unsafe markup.
- HTML Embed.

Patches

The problem has been recognized and patched. The fix will be available in version 43.1.1 (and above), and explicitly in version 41.3.2.

Workarounds

It's highly recommended to update to the version 43.1.1 or higher. However, if the update is not an option, we recommend disabling the block toolbar plugin.

For more information

Email us at [email protected] if you have any questions or comments about this advisory.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ckeditor5`	≥ 40.0.0&&< 43.1.1	43.1.1`npm install ckeditor5@43.1.1`
📦npm	`@ckeditor/ckeditor5-clipboard`	≥ 40.0.0&&< 43.1.1	43.1.1`npm install @ckeditor/ckeditor5-clipboard@43.1.1`

Affected Products

1 product · 1 configurations

Application

ckeditor5ckeditor

≥ 40.0.0 && < 43.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckeditor5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ckeditor5 to 43.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45613 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact During a recent internal audit, we identified a Cross-Site Scripting (XSS) vulnerability in the CKEditor 5 clipboard package. This vulnerability could be triggered by a specific user action, leading to unauthorized JavaScript code execution, if the attacker managed to insert a malicious content into the editor, which might happen with a very specific editor configuration. This vulnerability affects **only** installations where the editor configuration meets the following criteria: 1. The [**Block Toolbar**](https://ckeditor.com/docs/ckeditor5/latest/getting-started/setup/toolbar.h