WordPress security changelog
CRITICAL CVE-2026-3296 Deferred

Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder: Code execution

Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account. The published affected range is <= 3.4.3.

CVE / CNA score 9.8 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder
Plugin slug
everest-forms
Affected
<= 3.4.3
Safe version
> 3.4.3
Published
Apr 08, 2026
Weakness
CWE-502 — Deserialization of Untrusted Data

This CVE was published Apr 08, 2026 and is one of 21 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder to a release after 3.4.3, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Everest Forms plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.4.3 via deserialization of untrusted input from form entry metadata. This is due to the html-admin-page-entries-view.php file calling PHP's native unserialize() on stored entry meta values without passing the allowed_classes parameter. This makes it possible for unauthenticated attackers to inject a serialized PHP object payload through any public Everest Forms form field. The payload survives sanitize_text_field() sanitization (serialization control characters are not stripped) and is stored in the wp_evf_entrymeta database table. When an administrator views entries or views an individual entry, the unsafe unserialize() call processes the stored data without class restrictions.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

Primary and upstream sources