# CVE-2026-15372: WP 2FA < 4.1.0 - Two-Factor Authentication Bypass via Passkeys Provider

> Attackers with valid passwords can bypass two-factor authentication in WP 2FA to fully access user accounts, including administrators.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-r795-xx32-3hg7

## What is CVE-2026-15372?

CVE-2026-15372 is a high-severity authentication bypass vulnerability in Unknown WP 2FA, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP 2FA  WordPress plugin before 4.1.0 does not validate the second authentication factor when one of its supported methods is selected at login, allowing an attacker who already knows a user's password to bypass two-factor authentication and fully access the account, including administrator accounts.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-15372 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15372 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15372 is a high-severity authentication bypass vulnerability in Unknown WP 2FA, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15372 exists.

Affected product: Unknown WP 2FA. 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-15372/ (Markdown: https://insights.sbomify.com/CVE-2026-15372/index.md)
```

## Sources

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

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