Unauthenticated PHP object injection via entry metadata
Published Apr 8, 2026 · Updated Apr 8, 2026
PHP object injection in WPEverest Everest Forms 3.4.3 and earlier allows remote attackers to submit serialized objects through public forms. The entries view passes stored wp_evf_entrymeta values to unserialize() without restricting allowed classes after sanitization preserves serialization control characters. Exploitation requires an administrator to view the poisoned entry, and further impact depends on an available PHP object gadget chain.
Summary
What happened
PHP object injection in WPEverest Everest Forms 3.4.3 and earlier allows remote attackers to submit serialized objects through public forms. The entries view passes stored wp_evf_entrymeta values to unserialize() without restricting allowed classes after sanitization preserves serialization control characters. Exploitation requires an administrator to view the poisoned entry, and further impact depends on an available PHP object gadget chain.
The record
- CVE
- CVE-2026-3296
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- WPEverest
- Product
- Everest Forms
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo