CVE-2026-3584
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Kali Forms plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.4.9 via the 'form_process' function. This is due to the 'prepare_post_data' function mapping user-supplied keys directly into internal placeholder storage, combined with the use of 'call_user_func' on these placeholder values. This makes it possible for unauthenticated attackers to execute code on the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Kali Forms WordPress plugin has a critical RCE vulnerability in versions up to 2.4.9. The 'prepare_post_data' function improperly maps user-supplied input keys directly into internal placeholder storage, and these values are subsequently executed via the 'call_user_func' function. This allows unauthenticated attackers to execute arbitrary server-side code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Kali Forms plugin versionCheck the plugin header in wp-content/plugins/kali-forms/inc Kali_Forms.php or readme.txt for the 'Version' field, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'kali_forms_version'Affected if The installed version is 2.4.9 or lower (e.g., 2.4.8, 2.4.7, 2.4.6, etc.)
-
Confirm the plugin is activeQuery WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%kali-forms%'Affected if The plugin appears in the active plugins list and the version check above is true
-
Verify the vulnerable function existsInspect the file wp-content/plugins/kali-forms/inc/class-Kali_Forms.php (or similar path) and search for the function 'prepare_post_data' that contains user input mapped to placeholders and call_user_func usageAffected if The function exists and uses call_user_func with unsanitized user input from $_POST or similar superglobals
-
Check if the vulnerable endpoint is exposedReview the plugin routing to identify which AJAX or form handler calls prepare_post_data; this is typically accessible at /wp-admin/admin-ajax.php or a public form submission endpointAffected if The endpoint does not require authentication (is_public or is called via wp_ajax_nopriv_ hooks) and the version is <=2.4.9
You are affected if Kali Forms plugin version is 2.4.9 or lower AND the plugin is active AND the prepare_post_data function with call_user_func is present and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately update Kali Forms to a version beyond 2.4.9, or disable the plugin until an update is available. Implement WAF rules as a temporary measure to block suspicious form submissions targeting the vulnerable endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3584 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data