Security readout for executives and security teams
Plain-English summary
CVE-2026-3584 is a critical flaw in the Kali Forms WordPress plugin. Reported affected versions are up to and including 2.4.9. An unauthenticated attacker may be able to run code on the web server, which can lead to full site compromise and data exposure.
Executive priority
Treat this as urgent for any internet-facing WordPress site using Kali Forms. The business risk is site takeover, data theft, malware placement, and service disruption. Patch or disable affected installations quickly.
Technical view
The issue is described as CWE-94 remote code execution in Kali Forms form_process. User-controlled keys are mapped by prepare_post_data into internal placeholder storage, then used with call_user_func. The CVSS 3.1 score is 9.8: network exploitable, low complexity, no privileges, no user interaction.
Likely exposure
Public WordPress sites running Kali Forms version 2.4.9 or earlier are the primary concern. Exposure is highest where forms are reachable by unauthenticated visitors.
Exploitation context
The provided sources state unauthenticated remote code execution is possible. The CVE is not listed as CISA KEV in the bundle, and no cited source here confirms active exploitation.
Researcher notes
Key evidence is the Wordfence advisory, CVE record, and WordPress Trac references. The source bundle identifies the vulnerable flow but does not provide a complete vendor remediation narrative or confirmed fixed version in the supplied text.
Mitigation direction
- Inventory WordPress sites for the Kali Forms plugin and version.
- Prioritize any site running Kali Forms 2.4.9 or earlier.
- Apply the vendor or WordPress.org plugin update that includes the fix.
- If no safe update is available, disable or remove the plugin temporarily.
- Review vendor and Wordfence guidance for any additional compensating controls.
Validation and detection
- Confirm whether Kali Forms is installed on each WordPress instance.
- Check the installed plugin version against 2.4.9 or earlier.
- Verify plugin code includes the changes from WordPress Trac changeset 3487024.
- Review web and application logs for unusual unauthenticated form submissions.
- After remediation, retest plugin functionality and confirm the version changed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3584 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6cecd06f-c064-49fd-b3fa-505a5a0c2e0b?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/kali-forms/tags/2.4.9/Inc/Frontend/class-form-processor.php#L697CVE reference
- https://plugins.trac.wordpress.org/changeset/3487024/kali-formsCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.