Skip to main content
VulnerabilityPublished

CVE-2026-5415: Advanced Google reCAPTCHA (WordPress plugin) · Authentication Bypass Using an Alternate Path or Channel

Affects Advanced Google reCAPTCHA (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
webfactoryAdvanced Google reCAPTCHAAffected
  • <=5.38
Fixed in–

AI-suggested

Users should monitor the vendor's advisory for updates. Until a fix is available, restrict backend user roles to trusted individuals only and consider disabling or removing the WP Captcha PRO plugin if possible. Avoid dismissing the plugin's welcome pointer to prevent nonce exposure.

Description

The WP Captcha PRO plugin for WordPress, specifically the Advanced Google reCAPTCHA premium version, contains an authentication bypass vulnerability in all versions up to and including 5.38. This flaw allows authenticated users with Subscriber-level access or higher to generate passwordless login links and authenticate as any user, including administrators, leading to full account takeover. The vulnerability arises from insufficient authorization checks in AJAX handlers combined with nonce exposure to low-privileged users.

References

Community reviews

Loading reviews…