Description
The WP Post Author WordPress plugin before 4.2.0 does not restrict the integration settings it returns to visitors, allowing unauthenticated users to read the reCAPTCHA secret key when one has been saved.
Published: 2026-10-29
Score: n/a
EPSS: n/a
KEV: No
Impact: Confidentiality Disclosure
Action: Patch
AI Analysis

Impact

The WP Post Author plugin before version 4.2.0 returns integration settings, including the reCAPTCHA secret key, to any visitor. This allows an unauthenticated user to read a secret that can be used to bypass or impersonate reCAPTCHA checks. The attack is straightforward: by sending a simple HTTP request to the plugin endpoint, the attacker obtains the key with zero authentication or authorization, exposing a critical credential and undermining the website's anti‑spam protection.

Affected Systems

Site owners running the WordPress plugin WP Post Author with any version older than 4.2.0 are affected. The vulnerability applies to all installations where the plugin stores a reCAPTCHA secret key, regardless of the WordPress core version or other plugins used.

Risk and Exploitability

Although no explicit CVSS score is provided, the vulnerability allows unauthenticated disclosure of a secret key, a high‑impact condition. The absence of requirement for attacker privileges means exploitation effort is low. No known public exploits or KEV listing indicate that this has not yet been actively leveraged, but the potential to compromise reCAPTCHA protection makes it a significant security risk for sites relying on the plugin for spam prevention.

Generated by OpenCVE AI on October 29, 2026 at 07:26 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the WP Post Author plugin to version 4.2.0 or later, which restricts access to integration settings.
  • If an update is not possible, modify the plugin or web server configuration so that the endpoint exposing the settings is accessible only to authenticated administrators.
  • After ensuring the key is no longer exposed, regenerate the reCAPTCHA secret key in the Google Admin console and update the plugin configuration with the new key.
  • Verify that no other components or plugins expose sensitive data and consider enabling additional logging for unexpected access to plugin endpoints.

Generated by OpenCVE AI on October 29, 2026 at 07:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 29 Oct 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Thu, 29 Oct 2026 06:15:00 +0000

Type Values Removed Values Added
Description The WP Post Author WordPress plugin before 4.2.0 does not restrict the integration settings it returns to visitors, allowing unauthenticated users to read the reCAPTCHA secret key when one has been saved.
Title WP Post Author < 4.2.0 - Unauthenticated reCAPTCHA Secret Key Disclosure
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-10-29T06:00:24.208Z

Reserved: 2026-10-10T22:33:32.817Z

Link: CVE-2026-108686

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-29T06:17:17.583

Modified: 2026-10-29T06:17:17.583

Link: CVE-2026-108686

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-29T07:30:14Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor