CVE-2026-12988

WP 2FA <= 3.1.1.1 - Authenticated (Subscriber+) Account Takeover

2026-06-23 00:00
Janger

Strategic Overview

Status
Patched in 3.1.1.2
Affected Plugin
WP 2FA – Two-factor authentication for WordPress
Affected Version
<= 3.1.1.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-12988
View all WP 2FA – Two-factor authentication for WordPress vulnerabilities

At a glance

CVE-2026-12988 is a medium-severity Missing Authorization vulnerability in the WP 2FA WordPress plugin, affecting versions <= 3.1.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.1.1.2; sites on affected versions should update now. Disclosed June 2026, reported by Janger.

Vulnerability Overview

The WP 2FA – Two-factor authentication for WordPress plugin for WordPress is vulnerable to accoutn takeover in all versions up to, and including, 3.1.1.1. This is due to the plugin not properly verifying an email during 2FA enrollment. This makes it possible for authenticated attackers, with subscriber-level access and above, to complete verification for other users gaining access to their account.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WP 2FA <= 3.1.1.1 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP 2FA the fix is 3.1.1.2: builds <= 3.1.1.1 are affected, anything from 3.1.1.2 onward is not.

Remediation

Update to version 3.1.1.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP 2FA 3.1.1.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-12988https://www.wordfence.com/threat-intel/vulnerabilities/id/f3063e92-e152-440d-bf02-b852ff87e319https://nvd.nist.gov/vuln/detail/CVE-2026-12988

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C