A vulnerability in the CKEditor Open Link plugin (versions prior to 1.0.5) allows execution of arbitrary JavaScript code by abusing the link href attribute. This is due to insufficient sanitization of user-supplied input in the href attribute, leading to a cross-site scripting (XSS) condition.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (POC) exploit for CVE-2024-37888, a cross-site scripting (XSS) vulnerability in the Open Link plugin for CKEditor 4. The exploit demonstrates that when the Open Link plugin (version < 1.0.5) is enabled in CKEditor 4, an attacker can inject a link with a `javascript:` URI (e.g., `<a href="javascript:alert('XSS Found')">XSS</a>`) into the editor. When a user clicks this link inside the editing area, arbitrary JavaScript is executed, leading to XSS. The repository includes detailed setup and reproduction instructions in the README, a demo CKEditor instance under `demo/ckeditor/`, and configuration files showing how to enable the vulnerable plugin. The main exploit payload is a simple HTML anchor tag with a `javascript:` URI. The attack vector is browser-based, requiring user interaction (clicking the link) within the CKEditor editing area. The repository also references several URLs for downloading CKEditor, the vulnerable plugin, and for viewing advisories and demos. No weaponized or framework-based code is present; this is a standalone POC exploit. The structure is typical for a vulnerability demonstration, with documentation, demo files, and configuration scripts. The exploit is not a detection script or a fake; it provides a working XSS demonstration for the specified CVE.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.