Everest Forms <= 3.6.2 - Insecure Direct Object Reference to Authenticated (Custom+) Arbitrary Entry/Form Disclosure and Deletion via MCP /tools/call JSON-RPC Endpoint
Strategic Overview
- Status
- Patched in 3.6.3
- Affected Plugin
- Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI
- Affected Version
<= 3.6.2- CVSS
- 6.5Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-89101
At a glance
CVE-2026-89101 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Everest Forms WordPress plugin, affecting versions <= 3.6.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Custom level or above. The issue is fixed in version 3.6.3; sites on affected versions should update now. Disclosed November 2026, reported by Trgomez.
Vulnerability Overview
The Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.6.2 via the get_entry due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with custom-level access and above, to view, read, and permanently delete forms and entries belonging to any other user — including personally identifiable information submitted through public contact and lead forms — regardless of form ownership.
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. A successful exploit has high impact on confidentiality.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Everest Forms <= 3.6.2 takes an account at Custom 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 Everest Forms the fix is 3.6.3: builds <= 3.6.2 are affected, anything from 3.6.3 onward is not.
Remediation
Update to version 3.6.3, 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: Everest Forms 3.6.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI
- 9.8CVE-2026-3296: Everest Forms <= 3.4.3 PHP Object Injection
CVE-2026-3296 - 9.8CVE-2025-3439: Everest Forms PHP Object Injection
CVE-2025-3439 - 9.8CVE-2025-1128: Everest Forms Arbitrary File Upload, Read, and Deletion
CVE-2025-1128 - 9.8CVE-2019-13575: Contact Form SQL Injection
CVE-2019-13575 - 8.1CVE-2026-62103: Everest Forms PHP Object Injection
CVE-2026-62103 - 8.1CVE-2026-5478: Everest Forms <= 3.4.4 Arbitrary File Read and Deletion
CVE-2026-5478 - 7.2CVE-2026-108491: Everest Forms Stored XSS
CVE-2026-108491 - 7.2CVE-2024-1812: Everest Forms <= 2.0.7 Server-Side Request Forgery
CVE-2024-1812
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C