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**: Arbitrary File Upload via REST API. <br>๐ฅ **Consequences**: Attackers upload PHP scripts disguised as SVGs. Result: **Remote Code Execution (RCE)** on the server.โฆ
๐ก๏ธ **Root Cause**: **CWE-434** (Unrestricted Upload of File with Dangerous Type). <br>๐ **Flaw**: The plugin fails to validate file types when uploading SVG files via the REST API endpoint `/wp-json/mapsvg/v1/svgfile`.
๐ฎ **Privileges**: Requires **Authenticated** access (Subscriber role or higher). <br>๐ **Data**: Full server control via uploaded Web Scripts (PHP). CVSS Score: **9.9 (Critical)**.
๐ฃ **Public Exp?**: **YES**. <br>๐ **PoC**: Available on GitHub (`Nxploited/CVE-2025-32682`). <br>๐ **Description**: Confirms arbitrary file upload via the specific REST endpoint.
Q7How to self-check? (Features/Scanning)
๐ **Self-Check**: Scan for installed **MapSVG Lite** plugin. <br>๐ **Version**: Check if version is **โค 8.5.34**. <br>๐ ๏ธ **Tool**: Use WPScan or manual version check in WordPress dashboard.
Q8Is it fixed officially? (Patch/Mitigation)
๐ฉน **Official Fix**: **Yes**. <br>๐ **Action**: Update MapSVG Lite to the latest version. <br>๐ **Ref**: Patchstack database confirms vulnerability details and fix availability.
Q9What if no patch? (Workaround)
๐ง **No Patch?**: **Disable** the plugin immediately. <br>๐ซ **Block**: Restrict access to `/wp-json/mapsvg/v1/svgfile` endpoint via WAF. <br>๐ **Verify**: Ensure no suspicious PHP files exist in upload directories.
Q10Is it urgent? (Priority Suggestion)
๐ฅ **Urgency**: **CRITICAL**. <br>โฑ๏ธ **Priority**: **Immediate Action Required**. <br>๐ **Risk**: CVSS 9.9. Active PoC exists. High likelihood of exploitation by automated bots targeting authenticated users.