CVE-2026-3296 json
Everest Forms <= 3.4.3 - Unauthenticated PHP Object Injection via Form Entry Metadata
published 7mo ago modified 3mo ago also EUVD-2026-20020
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Is CVE-2026-3296 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 7mo ago
Exploit prediction
3.59% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Everest Forms WordPress Plugin <= 3.4.3 - PHP Object Injection nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/2693ae37-790d-4b18-a9ec-054c8c27b8bc?source=cve
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.4.3/includes/admin/views/html-admin-page-entries-view.php#L133
- plugins.trac.wordpress.org /browser/everest-forms/trunk/includes/admin/views/html-admin-page-entries-view.php#L133
- plugins.trac.wordpress.org /browser/everest-forms/tags/3.4.3/includes/evf-core-functions.php#L5594
- plugins.trac.wordpress.org /changeset/3489938/everest-forms/tags/3.4.4/readme.txt?old=3464753&old_path=everest-forms%2Ftags%2F3.4.3%2Frea
- plugins.trac.wordpress.org /changeset?old_path=/everest-forms/tags/3.4.3&new_path=/everest-forms/tags/3.4.4
Sources
- CVE List CVE-2026-3296
- NVD CVE-2026-3296
Fencer Intel 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.