Loading vulnerability…
CVE-2024-25293 is a critical remote code execution vulnerability in mjml-app versions 3.0.4 and 3.1.0-beta. The flaw is triggered via the href attribute, which is improperly handled, allowing attackers to inject and execute arbitrary code on the target system. The vulnerability does not require authentication or user interaction, making exploitation trivial for remote attackers. Proof-of-concept code is publicly available, increasing the risk of exploitation in the wild.
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 demonstrates a proof-of-concept exploit for CVE-2024-25293, a local code execution vulnerability in mjml-app versions 3.0.4-win and 3.1.0-beta on Windows. The exploit leverages the application's mishandling of the 'href' attribute in 'mj-button' tags within MJML files, allowing an attacker to craft a malicious MJML project. When a victim opens the project and interacts with the malicious button, arbitrary local files or executables (such as calc.exe or a crafted text file) can be executed on the victim's system. The repository contains a README.md with detailed explanation and a sample MJML file (jruru.mjml) that includes the exploit payload. The attack vector is local, requiring user interaction with a malicious MJML file. No network endpoints are involved; the exploit targets local file paths and executables.
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.