# CVE-2026-120407: Contact Form 7 < 6.2.5 - Editor+ Sensitive User Data Disclosure via Form Default Values


- **Severity:** Medium 4.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-q75w-p7rr-vmcf

## What is CVE-2026-120407?

CVE-2026-120407 is a medium-severity vulnerability in Unknown Contact Form 7, published on 13 Nov 2026. 

### Official description

The Contact Form 7 WordPress plugin before 6.2.5 does not restrict which user properties a form field's default value can be populated from, allowing users with the Editor role and above to obtain the password hash and sensitive user meta (such as two-factor secrets) of higher-privileged users, including administrators, who view and submit the form.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-120407?


## How do I fix CVE-2026-120407?

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

## Is CVE-2026-120407 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120407 and fix it if it is affected.

What it is: CVE-2026-120407 is a medium-severity vulnerability in Unknown Contact Form 7, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120407 in the wild and no public exploit code.

Affected product: Unknown Contact Form 7. 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-2026-120407/ (Markdown: https://insights.sbomify.com/CVE-2026-120407/index.md)
```

## Sources

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

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