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**: Unauthenticated Arbitrary Plugin Installation. 💥 **Consequences**: Attackers can install malicious plugins (webshells), leading to full site compromise, data theft, and server takeover.…
🛡️ **CWE-862**: Missing Authorization. 🔍 **Flaw**: The `install_or_activate_addon_plugins()` function lacks a capability check. 🗝️ **Weakness**: The nonce hash is weak, allowing bypass of authentication checks.
👑 **Privileges**: Unauthenticated access (No login needed). 📂 **Data**: Full control over the WordPress installation. 🕸️ **Action**: Install arbitrary PHP plugins/webshells.…
🔓 **Public Exp?**: **YES**. 📂 **PoC**: Available on GitHub (gmh5225). 🤖 **Scanner**: Nuclei templates available (projectdiscovery). 📝 **Method**: POST request to REST API with malicious ZIP URL.
Q7How to self-check? (Features/Scanning)
🔍 **Check**: Scan for REST endpoint `/autonami-app/plugin/install_and_activate`. 📊 **Tool**: Use Nuclei with CVE-2025-1562 template. 📦 **Verify**: Check plugin version in WordPress admin (if accessible) or HTTP headers.
Q8Is it fixed officially? (Patch/Mitigation)
🛡️ **Fixed?**: **YES**. 📅 **Patch Date**: June 18, 2025. 🔄 **Update**: Upgrade to version **> 3.5.3**. 📖 **Ref**: WordPress Trac changeset 3305437 addresses the API loader and admin class.
Q9What if no patch? (Workaround)
🚧 **Workaround**: If unpatched, **disable the plugin** immediately. 🚫 **Block**: Restrict access to `/wp-json/autonami-app/` via WAF. 🔒 **Hardening**: Disable REST API for non-authenticated users if possible.
Q10Is it urgent? (Priority Suggestion)
🔥 **Urgency**: **CRITICAL**. 🚨 **Priority**: **P0**. ⚡ **Reason**: Unauthenticated RCE potential via plugin install. 🏃 **Action**: Patch immediately or disable plugin to prevent total site takeover.