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

Status: published. Published: 2026-11-13. Updated: 2026-11-13.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Contact Form 7: ≥ 0; < 6.2.5 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-200

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/a981358b-6736-4d46-9352-b57a11dbcb54/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/a981358b-6736-4d46-9352-b57a11dbcb54/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-120407; retrieved 2026-11-13; source updated 2026-11-13

Revision: d66c9db08927e158afa68e8ca9a71012fb157d22d2d6a7bc7be0e1e10018b8dc

Canonical: https://y2.dev/cve/CVE-2026-120407

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.