# CVE-2025-12628: WP 2FA < 3.0.0 - Second Factor Bypass

> Attackers can bypass two-factor authentication by brute-forcing low-entropy backup codes, leading to account takeover in WP 2FA plugin users.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 24 Nov 2025
- **Updated:** 24 Nov 2025
- **Also known as:** GHSA-92fr-wf6q-p5h2

## What is CVE-2025-12628?

CVE-2025-12628 is a medium-severity vulnerability in Unknown WP 2FA, published on 24 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP 2FA WordPress plugin does not generate backup codes with enough entropy, which could allow attackers to bypass the second factor by brute forcing them

## Which versions are affected by CVE-2025-12628?


## How do I fix CVE-2025-12628?

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

## Is CVE-2025-12628 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12628 and fix it if it is affected.

What it is: CVE-2025-12628 is a medium-severity vulnerability in Unknown WP 2FA, published on 24 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12628 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-2025-12628/ (Markdown: https://insights.sbomify.com/CVE-2025-12628/index.md)
```

## Sources

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

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