The WP Post Author WordPress plugin before 4.2.0 does not restrict the integration settings it returns to visitors
Source GCVE Database
Not known to be exploited : upgrade to 4.2.0 soon.
Data as of 29 Oct 2026, 07:11 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 4.2.0
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 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 29 Oct 2026.
What to do
Upgrade WP Post Author to 4.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Post Author | Affected
| Fixed in
|
AI-suggested
A fixed version 4.2.0 or later should be applied once available.
Description
The WP Post Author WordPress plugin versions before 4.2.0 have a vulnerability where integration settings are not properly restricted. This flaw allows unauthenticated users to access and read the reCAPTCHA secret key if it has been saved in the plugin settings.