CVE-2026-108686

WP Post Author < 4.2.0 - Unauthenticated reCAPTCHA Secret Key Disclosure

Published Oct 29, 2026 CVSS 3.1 · 3.7 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical 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

The CVSS score of 3.7 indicates a low to moderate severity for confidentiality disclosure. Unauthenticated users can easily retrieve the reCAPTCHA secret key, which offers the attacker the ability to forge or bypass reCAPTCHA verification. No explicit exploit is required and no logs are produced, making exploitation effort very low. While no known public exploits or KEV listing are reported, the risk remains significant for sites heavily relying on the plugin for spam prevention.

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 12:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}

Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions wp Post Author
Vendors & Products Wordpress-extensions
Wordpress-extensions wp Post Author
Type Values Removed Values Added
Weaknesses CWE-200
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
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 29, 2026, 10:56 AM
Reserved
Oct 10, 2026, 10:33 PM
Status
Deferred
Published
Oct 29, 2026, 6:17 AM
Modified
Oct 29, 2026, 3:18 PM