CVE-2026-5415

WP Captcha PRO <= 5.38 - Authenticated (Subscriber+) Authentication Bypass via Temporary Login Link

2026-06-05 05:58
Nguyen Ngoc Duc (duc193)

Strategic Overview

Status
Patched in 5.39
Affected Version
<= 5.38
CVSS
8.8High
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2026-5415
View all Advanced Google reCAPTCHA vulnerabilities

At a glance

CVE-2026-5415 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Advanced Google reCAPTCHA WordPress plugin, affecting versions <= 5.38. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.39; sites on affected versions should update now. Disclosed June 2026, reported by Nguyen Ngoc Duc (duc193).

Vulnerability Overview

The WP Captcha PRO (the premium version of the Advanced Google reCAPTCHA plugin, both have the same slug) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 5.38. This is due to the ajax_run_tool() AJAX handler relying solely on a nonce check (check_ajax_referer) for security without performing any capability check, combined with the create_temporary_link tool allowing the generation of passwordless login links for arbitrary users, and the handle_temporary_links() function authenticating visitors via these links without any additional authorization validation. The required nonce is exposed to all authenticated backend users (including Subscribers) via wp_localize_script() on all non-settings admin pages when the plugin's welcome pointer has not been dismissed. This makes it possible for authenticated attackers, with Subscriber-level access and above, to bypass normal authentication and log in as any user, including Administrators, resulting in complete account takeover.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-288: Authentication Bypass Using an Alternate Path or Channel

Advanced Google reCAPTCHA <= 5.38 carries this weakness at ajax_run_tool(), and reaching it takes an account at Subscriber level or above. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Advanced Google reCAPTCHA the fix is 5.39: builds <= 5.38 are affected, anything from 5.39 onward is not.

Remediation

Update to version 5.39, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Advanced Google reCAPTCHA 5.39 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C