Kali Forms <= 2.4.16 - Authenticated (Contributor+) Insecure Direct Object Reference to Post Metadata Disclosure
Strategic Overview
- Status
- Patched in 2.4.17
- Affected Plugin
- Kali Forms — Contact Form & Drag-and-Drop Builder
- Affected Version
<= 2.4.16- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-11580
At a glance
CVE-2026-11580 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Kali Forms WordPress plugin, affecting versions <= 2.4.16. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.4.17; sites on affected versions should update now. Disclosed June 2026, reported by Muni Nitish Kumar Yaddala.
Vulnerability Overview
The Kali Forms — Contact Form & Drag-and-Drop Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.4.16 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to expose post metadata.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Kali Forms <= 2.4.16 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Kali Forms the fix is 2.4.17: builds <= 2.4.16 are affected, anything from 2.4.17 onward is not.
Remediation
Update to version 2.4.17, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Kali Forms 2.4.17 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Kali Forms — Contact Form & Drag-and-Drop Builder
- 9.8CVE-2026-3584: Kali Forms <= 2.4.9 Remote Code Execution
CVE-2026-3584 - 8.8CVE-2020-36717: Kali Forms <= 2.1.1 Cross-Site Request Forgery
CVE-2020-36717 - 8.6CVE-2020-36712: Kali Forms <= 2.1.1 Arbitrary Post Deletion
CVE-2020-36712 - 8.1CVE-2026-16144: Kali Forms <= 2.4.20 Remote Code Execution
CVE-2026-16144 - 8.1CVE-2026-59542: Kali Forms Arbitrary File Deletion
CVE-2026-59542 - 7.6CVE-2024-1217: Contact Form builder… Arbitrary Plugin Deactivation
CVE-2024-1217 - 7.2CVE-2026-65446: Kali Forms <= 2.4.18 Stored Cross-Site Scripting
CVE-2026-65446 - 7.2CVE-2026-15395: Kali Forms <= 2.4.18 Stored Cross-Site Scripting
CVE-2026-15395
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C