# CVE-2025-3439: Deserialization in Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder

> Unauthenticated attackers can inject PHP objects via untrusted input, potentially leading to code execution or data theft if a POP chain exists.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-jq7g-h856-ccpg

## What is CVE-2025-3439?

CVE-2025-3439 is a critical unsafe deserialization vulnerability in wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Everest Forms – Contact Form, Quiz, Survey, Newsletter & Payment Form Builder for WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1.1 via deserialization of untrusted input from the 'field_value' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-3439?

It affects 1 product.


Products: Wpeverest Everest Forms.

## How do I fix CVE-2025-3439?

No fix has been published for CVE-2025-3439 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3439 being exploited?

There is no known exploitation of CVE-2025-3439 in the wild and no public exploit code.

## Other vulnerabilities in wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder

- [CVE-2025-1128](https://insights.sbomify.com/CVE-2025-1128/): Everest Forms <= 3.0.9.4 - Unauthenticated Arbitrary File Upload, Read, and Deletion (critical 9.8)
- [CVE-2019-13575](https://insights.sbomify.com/CVE-2019-13575/): SQL injection in n/a (critical 9.8)
- [CVE-2025-5927](https://insights.sbomify.com/CVE-2025-5927/): Everest Forms (Pro) <= 1.9.4 - Unauthenticated Path Traversal to Arbitrary File Deletion (high 7.5)
- [CVE-2024-1812](https://insights.sbomify.com/CVE-2024-1812/): Everest Forms <= 2.0.7 - Unauthenticated Server-Side Request Forgery via font_url (high 7.2)
- [CVE-2025-26841](https://insights.sbomify.com/CVE-2025-26841/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3439 and fix it if it is affected.

What it is: CVE-2025-3439 is a critical unsafe deserialization vulnerability in wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3439 in the wild and no public exploit code.

Affected product: wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3439/ (Markdown: https://insights.sbomify.com/CVE-2025-3439/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3439
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3439
- OSV: https://osv.dev/vulnerability/CVE-2025-3439

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3439/
Summaries are generated and may contain mistakes; the official description above is the record.