CVE-2026-91153 json
Everest Forms <= 3.6.2 - Unauthenticated Sensitive Information Exposure via Smart-Tag Injection in Smart-Tag Injection in Form Field Values ({post_meta key=...})
published 2026-10-29 11 d ago modified 2026-10-29 11 d ago also EUVD-2026-112691
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- 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 Sensitive Information Exposure in all versions up to, and including, 3.6.2 via the process. This makes it possible for unauthenticated attackers to extract arbitrary WordPress post meta values — including license keys, API tokens, SMTP credentials, and Stripe or AWS secrets stored on any post type — via form submission notification emails or stored entries. The submission nonce is publicly rendered in every embedded form and can additionally be minted anonymously via the nopriv everest_forms_get_form_update_nonce action, meaning no account or prior authentication of any kind is required to complete the exploit.
Patch / fix
- github.com/themegrill/everest-forms#1669 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 11 d ago
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- github.com /themegrill/everest-forms/pull/1669/changes
- wordfence.com /threat-intel/vulnerabilities/id/b820a342-3aaa-4782-9d82-afe53028b72c?source=cve
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/class-evf-smart-tags.php#L503
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/class-evf-form-task.php#L731
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/class-evf-form-task.php#L261
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/class-evf-ajax.php#L681
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/class-evf-ajax.php#L2342
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.6.1/includes/shortcodes/class-evf-shortcode-form.php#L370
- plugins.trac.wordpress.org /changeset/3747723/everest-forms/trunk/includes/class-evf-form-task.php
Sources
- CVE List CVE-2026-91153
- NVD CVE-2026-91153
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.