The Contact Form 7 WordPress plugin before 6.2.5 does not restrict which user properties a form field's default value
Source GCVE Database
Not known to be exploited : upgrade to 6.2.5 soon.
Data as of 13 Nov 2026, 07:55 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 6.2.5
Exploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.
What to do
Upgrade Contact Form 7 (WordPress plugin) to 6.2.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Contact Form 7 | Affected
| Fixed in
|
AI-suggested
Upgrade Contact Form 7 to version 6.2.5 or later, where this issue is fixed.
Description
A vulnerability in the Contact Form 7 WordPress plugin before version 6.2.5 allows users with Editor role or higher to access sensitive user information. Specifically, these users can obtain password hashes and sensitive user metadata, including two-factor authentication secrets, of higher-privileged users such as administrators by exploiting the form field's default value population mechanism.