The WP Post Author WordPress plugin before 4.2.0 does not check that the account was created before updating its
Source GCVE Database
Not known to be exploited : upgrade to 4.2.0 when convenient.
Data as of 29 Oct 2026, 07:10 UTC
Rated Medium 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
Upgrade the WP Post Author plugin to version 4.2.0 or later, where this vulnerability is fixed. No other mitigation guidance is provided in the source data.
Description
The WP Post Author WordPress plugin versions prior to 4.2.0 contain a vulnerability where the plugin does not verify that a user account was created before allowing profile updates during front-end registration. This flaw permits unauthenticated users to overwrite the display name, nickname, and website fields of the first user account, which is typically the administrator account.