# CVE-2026-12988: WP 2FA < 3.1.1.2 - Account Takeover via 2FA Setup Email Binding

> Attackers with valid credentials can hijack accounts by binding 2FA setup to their own email due to missing ownership verification.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/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:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-ghqr-w463-c6wr

## What is CVE-2026-12988?

CVE-2026-12988 is a medium-severity vulnerability in Unknown WP 2FA, published on 14 Jul 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 3.1.1.2 does not verify that the email address supplied during two-factor authentication setup belongs to the user, allowing an attacker who has obtained a user's credentials to redirect the setup verification code to an attacker-controlled email address and take over the account.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12988 is a medium-severity vulnerability in Unknown WP 2FA, published on 14 Jul 2026. 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-2026-12988 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-12988/ (Markdown: https://insights.sbomify.com/CVE-2026-12988/index.md)
```

## Sources

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

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