0.0
NA
CVE-2026-12988
WP 2FA < 3.1.1.2 - Account Takeover via 2FA Setup Email Binding
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.

INFO

Published Date :

July 14, 2026, 6:17 a.m.

Last Modified :

July 14, 2026, 6:17 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-12988 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Update the WP 2FA plugin to version 3.1.1.2 or later to fix account takeover vulnerability.
  • Update the WP 2FA plugin to version 3.1.1.2 or later.
  • Verify email verification for two-factor authentication is secure.
  • Review security settings for two-factor authentication.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-12988.

URL Resource
https://wpscan.com/vulnerability/8aa6bf91-54ee-4326-a477-31f42284be22/
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-12988 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-12988 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-12988 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-12988 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 14, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'Unknown', 'product': 'WP 2FA', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '3.1.1.2', 'versionType': 'semver'}], 'defaultStatus': 'unaffected'}]
    Added 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.
    Added Reference https://wpscan.com/vulnerability/8aa6bf91-54ee-4326-a477-31f42284be22/
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.