CVE-2026-89101 json
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
published 2026-11-06 2 d ago modified 2026-11-06 2 d ago also EUVD-2026-118188
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/1fabe52a-b51e-4383-ac88-8f30e083c9bb?source=cve
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L669
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L686
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L563
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L62
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L30
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L34
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L22
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-handlers.php#L46
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-mcp-server.php#L52
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/abilities/class-evf-abilities-registry.php#L74
- plugins.trac.wordpress.org /changeset/3704878/everest-forms/trunk/includes/abilities/class-evf-abilities-handlers.php
Sources
- CVE List CVE-2026-89101
- NVD CVE-2026-89101
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.