# CVE-2026-103514: WP 2FA < 4.1.0 - Two-Factor Authentication Bypass via TOTP Code Replay

> Attackers can bypass two-factor authentication by replaying valid TOTP codes, potentially taking over administrator accounts in WP 2FA plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** 3 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-fh83-crgf-9w82

## What is CVE-2026-103514?

CVE-2026-103514 is a high-severity authentication bypass vulnerability in Unknown WP 2FA, published on 3 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP 2FA  WordPress plugin before 4.1.0 does not invalidate a time-based one-time passcode once it has been used, allowing an attacker who knows an account's password and has observed a valid code within its validity window to replay it and bypass two-factor authentication, including on administrator accounts.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-103514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103514 is a high-severity authentication bypass vulnerability in Unknown WP 2FA, published on 3 Oct 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-103514 in the wild and no public exploit code.

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-103514/ (Markdown: https://insights.sbomify.com/CVE-2026-103514/index.md)
```

## Sources

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

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