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.