# CVE-2026-5415: WP Captcha PRO <= 5.38 - Authenticated (Subscriber+) Authentication Bypass via Temporary Login Link

> Authenticated subscribers can bypass authentication and log in as any user, including administrators, due to missing capability checks in the WP Captcha PRO plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-f32q-xh2j-mm3g

## What is CVE-2026-5415?

CVE-2026-5415 is a high-severity authentication bypass vulnerability in webfactory Advanced Google reCAPTCHA, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

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

## Which versions are affected by CVE-2026-5415?


## How do I fix CVE-2026-5415?

No fix has been published for CVE-2026-5415 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5415 being exploited?

There is no known exploitation of CVE-2026-5415 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-5415 WP Captcha PRO Authenticated Authentication Bypass Exploit (github_poc): https://github.com/izxci/CVE-2026-5415

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5415 and fix it if it is affected.

What it is: CVE-2026-5415 is a high-severity authentication bypass vulnerability in webfactory Advanced Google reCAPTCHA, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5415 in the wild and no public exploit code.

Affected product: webfactory Advanced Google reCAPTCHA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5415/ (Markdown: https://insights.sbomify.com/CVE-2026-5415/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5415
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5415
- OSV: https://osv.dev/vulnerability/CVE-2026-5415

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5415/
Summaries are generated and may contain mistakes; the official description above is the record.