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)
🛡️ **Root Cause**: Missing Capability Check (CWE-862). The `install_and_activate_plugin_from_external()` function lacks proper authorization validation, allowing anyone to trigger it.
🔥 **Exploits**: YES. Multiple PoCs exist on GitHub (e.g., RandomRobbieBF, Nxploited). Automated scanning templates available via ProjectDiscovery Nuclei.
Q7How to self-check? (Features/Scanning)
🔍 **Self-Check**: Scan for GutenKit plugin version <= 2.1.0. Check if the REST API endpoint `install-active-plugin` is accessible without auth. Use Nuclei templates for automated detection.
Q8Is it fixed officially? (Patch/Mitigation)
✅ **Fixed**: YES. Update to version **2.1.1** or later. The vendor has released a patch addressing the missing capability check in the ActivePluginData.php file.
Q9What if no patch? (Workaround)
🚧 **No Patch?**: Disable the plugin immediately. Restrict access to the WordPress REST API endpoints via WAF or server config. Monitor for suspicious plugin installations.
Q10Is it urgent? (Priority Suggestion)
🔴 **Urgency**: CRITICAL. CVSS Score is **9.8 (Critical)**. Unauthenticated remote code execution potential. Patch immediately to prevent takeover.