Loading vulnerability…
CVE-2024-47875 is a critical mutation cross-site scripting (mXSS) vulnerability in DOMPurify, the HTML/MathML/SVG sanitization library. The issue is described as a nesting-based mXSS flaw, meaning crafted nested markup can survive sanitization and then mutate during browser DOM parsing into executable script-bearing content. As a result, DOMPurify may incorrectly treat attacker-controlled input as safe. The vulnerability affects vulnerable DOMPurify releases prior to the fixed versions 2.5.0 and 3.1.3. The issue has been noted downstream in products bundling vulnerable DOMPurify versions, including Jira Software Data Center and Server, Jira Service Management Data Center and Server, Siemens COMOS, and OX App Suite frontend.
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 (1 hidden).
This repository is a proof-of-concept (PoC) exploit for CVE-2024-47875 (also referenced as CVE-2025-22131), a Cross-Site Scripting (XSS) vulnerability in PhpSpreadsheet versions prior to 2.2.2, 2.1.2, and 1.29.4. The exploit leverages the generateNavigation() function's failure to sanitize sheet names during XLSX-to-HTML conversion, allowing an attacker to inject arbitrary JavaScript via a crafted XLSX file. The main file, 'exploit.py', is a Python script that automates the creation of malicious XLSX files with various XSS payloads (cookie theft, redirect, alert, keylogger, form hijack, data exfiltration, or custom JavaScript). It also includes a built-in HTTP server to receive callbacks from the victim's browser and can upload the malicious file to a specified endpoint on the target application. The README provides detailed usage instructions and describes the exploit's features. The repository is structured with a single exploit script, a README, and a license file. The exploit is operational as a PoC and demonstrates the impact of the vulnerability, but does not include weaponized or framework-level automation.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.