CVE-2024-25293
Published: 01 March 2024
Summary
CVE-2024-25293 is a critical-severity Code Injection (CWE-94) vulnerability in Mjml Mjml App. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked in the top 4.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
mjml-app versions 3.0.4 and 3.1.0-beta contain a code-injection flaw (CWE-94) that permits remote code execution when an attacker supplies a crafted value in an href attribute. The vulnerability carries a CVSS 3.1 score of 9.3 with an attack vector rated local yet scope changed, resulting in complete loss of confidentiality, integrity, and availability on the affected host.
An unauthenticated local actor can trigger the flaw without user interaction, causing the application to execute arbitrary commands under the privileges of the mjml-app process. Successful exploitation therefore yields full control over the target system, including the ability to read or modify any accessible data and to install persistent malware.
Public proof-of-concept code demonstrating the attack has been published on GitHub. The current EPSS score of 0.1993 matches the observed peak, indicating moderate and stable exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-22629
Vulnerability details
mjml-app versions 3.0.4 and 3.1.0-beta were discovered to contain a remote code execution (RCE) via the href attribute.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The RCE vulnerability in mjml-app via the href attribute allows adversaries to exploit the client-side application for arbitrary code execution when processing malicious MJML input.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.
Dynamically generated code can be produced and executed inside the isolated chamber, preventing host compromise from code-injection payloads.
Validates inputs used in dynamic code generation to block injected directives.
Directly prevents execution of attacker-supplied code written into data memory regions.