Skip to main content
CVE-2026-108686VulnerabilityPublished

The WP Post Author WordPress plugin before 4.2.0 does not restrict the integration settings it returns to visitors

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-108686· High

Not known to be exploited : upgrade to 4.2.0 soon.

Data as of 29 Oct 2026, 07:11 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
WP Post AuthorAffected
  • <4.2.0
Fixed in
  • 4.2.0

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.

References

Community reviews

Loading reviews…