Elementor Website Builder for WordPress before version 3.4.8 does not sanitize or escape user-controlled input appended to the DOM from a malicious URL hash fragment. This permits DOM-based cross-site scripting.
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 containerized lab environment simulating a DOM-based Cross-Site Scripting (XSS) vulnerability in the Elementor Website Builder WordPress plugin (CVE-2021-24891). The structure includes a Dockerfile for setting up a WordPress 5.8 instance with the vulnerable plugin, and a full WordPress directory tree under 'app/'. The README.md gives detailed instructions for launching the lab using Docker or GitHub Codespaces, and explains the vulnerability: the Elementor editor's JavaScript reads the URL hash and injects it into the DOM without sanitization, allowing an attacker to craft a link with a malicious JavaScript payload in the hash fragment. When a logged-in admin visits such a link, the script executes in their browser context, potentially leading to session hijacking or site compromise. The main attack vector is browser-based, requiring social engineering to get an admin to click a crafted link. The repository is educational, not weaponized, and does not include automated exploitation scripts, but provides a realistic environment for manual exploitation and study of the vulnerability.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.