Unauthenticated RCE in Kali Forms for WordPress
CVE-2026-3584 is a remote code execution vulnerability in the Kali Forms plugin for WordPress affecting all versions up to and including 2.4.9. The flaw is reachable via the plugin's 'form_process' function. According to the provided content, the root cause is that the 'prepare_post_data' function maps user-supplied keys directly into internal placeholder storage, and those placeholder values are later invoked via 'call_user_func'. This unsafe handling of attacker-controlled input allows an unauthenticated remote attacker to influence callable execution on the server, resulting in arbitrary code execution.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
The repository is a small standalone exploit project with two files: a long README and a Python script, mass_scanner.py. The README documents CVE-2026-3584, describing an unauthenticated RCE and privilege-escalation issue in the WordPress Kali Forms plugin <= 2.4.9 via the publicly exposed AJAX action kaliforms_form_process. It explains the attack chain: send POST requests to /wp-admin/admin-ajax.php with action=kaliforms_form_process and attacker-controlled fields such as data[thisPermalink] or data[entryCounter] to invoke arbitrary PHP callbacks, including phpinfo() for code execution validation and wp_set_auth_cookie for session creation. The Python code is the operational component. It is a multithreaded mass scanner that accepts a file of targets, normalizes URLs by probing HTTPS/HTTP, and uses requests plus BeautifulSoup for reconnaissance and exploitation workflow. Based on the visible code and README description, the scanner performs several stages: WordPress REST API enumeration through /wp-json/wp/v2/users and /wp-json/wp/v2/posts, site crawling/form discovery, exploitation attempts against the vulnerable AJAX endpoint, and post-exploitation handling of WordPress cookies. It creates result and result_cookie directories, logs progress in a thread-safe way, tracks scan statistics, and writes per-host HTTP request templates containing harvested cookies for direct reuse against /wp-admin/. This is not merely a detector: it is intended to exploit targets at scale. Its main capabilities are reconnaissance of WordPress targets, identification of likely vulnerable Kali Forms deployments, unauthenticated callback execution through the plugin’s form_process logic, and privilege escalation by generating valid WordPress auth cookies. The code appears to be a standalone Python PoC/operational scanner rather than part of a larger exploit framework.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability identified as CVE-2026-3584 is referenced in a GitHub pull request for creation/update of a Nuclei template, but no technical details about the flaw are provided in the content.
A remote code execution vulnerability in the Kali Forms plugin for WordPress affecting all versions up to and including 2.4.9, allowing unauthenticated attackers to execute code on the server.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.