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**: Remote Code Execution (RCE) in Kali Forms. 💥 **Consequences**: Attackers can inject and execute arbitrary PHP code on the server. This leads to full server compromise, data theft, and site defacement.
Q2Root Cause? (CWE/Flaw)
🛡️ **CWE-94**: Improper Control of Generation of Code (Code Injection). 🔍 **Flaw**: The `form_process` function uses `prepare_post_data` to map user-supplied keys directly to internal placeholders.…
📦 **Vendor**: wpchill. 📦 **Product**: Kali Forms — Contact Form & Drag-and-Drop Builder. 📉 **Affected Versions**: Version **2.4.9 and earlier**. ✅ **Fixed**: Version 2.4.9+ (implied by '2.4.9 and earlier').
Q4What can hackers do? (Privileges/Data)
👑 **Privileges**: Full Server Control (Root/Admin). 📂 **Data**: Access to all database contents, user credentials, and server files. ⚡ **Impact**: High (CVSS 9.8).…
🔓 **Auth Required**: **None**. Unauthenticated attackers can exploit this. 🌐 **Network**: Remote (AV:N). 🎯 **Complexity**: Low (AC:L). No user interaction needed (UI:N). Extremely easy to exploit.
Q6Is there a public Exp? (PoC/Wild Exploitation)
🔥 **Public Exploit**: **Yes**. A Nuclei template is available on GitHub (projectdiscovery/nuclei-templates). 🌍 **Wild Exploitation**: High risk due to simplicity and public PoC availability.
Q7How to self-check? (Features/Scanning)
🔍 **Self-Check**: Scan for Kali Forms plugin version <= 2.4.9. 🧪 **Test**: Use Nuclei template `CVE-2026-3584.yaml`. 📝 **Manual**: Check if `form_process` handles untrusted input safely.…
🛠️ **Official Fix**: Yes. Update to **Kali Forms version 2.4.9 or later**. 📢 **Source**: WordPress plugin repository changeset 3487024. 📅 **Published**: March 20, 2026.
Q9What if no patch? (Workaround)
🚧 **Workaround**: If patching is delayed, **disable the Kali Forms plugin** immediately. 🚫 **Block**: Restrict access to `/wp-admin/` and form endpoints via WAF rules.…