This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis β
Q1What is this vulnerability? (Essence + Consequences)
π¨ **Essence**: Mautic < 5.2.3 has a critical flaw in Asset Editing. π **Consequences**: Attackers achieve **Remote Code Execution (RCE)** and can **delete files** recursively via path traversal.β¦
π― **Affected**: **Mautic** marketing automation software. π¦ **Version**: All versions **prior to 5.2.3**. π¦ **Component**: `mautic/core`. β οΈ If you are running 5.2.2 or older, you are at risk.
Q4What can hackers do? (Privileges/Data)
π **Hackers Can**: 1. Execute arbitrary PHP code (RCE). ποΈ 2. Recursively delete ANY directory the web-user can access. π **Privileges**: Limited to web-user permissions, but still catastrophic for data integrity.
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: **Medium**. π« **Auth Required**: Yes, attacker must be **Authenticated**. π **Network**: Remote (AV:N). π **Complexity**: Low (AC:L). No UI interaction needed (UI:N).
Q6Is there a public Exp? (PoC/Wild Exploitation)
π» **Exploits Available**: Yes! Public PoCs exist on GitHub. π [mallo-m/CVE-2024-47051](https://github.com/mallo-m/CVE-2024-47051) demonstrates Authenticated RCE. π Wild exploitation is likely given the low complexity.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: 1. Check Mautic version (< 5.2.3). π 2. Inspect `/assets/view/{assetID}` route for file upload capabilities. π 3. Look for improper sanitization of file extensions/types in asset editing forms. πΈ
Q8Is it fixed officially? (Patch/Mitigation)
β **Fixed**: Yes! Upgrade to **Mautic 5.2.3** or later. π‘οΈ **Official Advisory**: GHSA-73gx-x7r9-77x2. π Patch addresses the sanitization flaws in asset handling.
π₯ **Urgency**: **HIGH**. π¨ CVSS Score indicates High Impact (C:H). π Published Feb 2025, PoCs already live. β‘ Immediate patching or mitigation is strongly recommended to prevent RCE and data loss.