dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12988

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP 2FA plugin fails to validate email ownership during 2FA setup. An authenticated attacker with valid WordPress credentials can supply an attacker-controlled email address during the 2FA enrollment process, receive the verification code at that email, and complete setup—binding the account to the attacker's email and enabling full account takeover via 2FA.

MitigationUpdate WP 2FA to version 3.1.2 or later. Until then, monitor for unauthorized 2FA enrollment events and consider disabling the plugin if not essential.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WP 2FA plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins and locate 'WP 2FA' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header or the readme.txt file in the plugin directory.
    Affected if The installed version is earlier than 3.1.2
  2. Confirm 2FA is enabled on the site
    Go to WP 2FA plugin settings page (usually under Users > 2FA or Settings > WP 2FA) and check if two-factor authentication is active and enforced for users.
    Affected if 2FA is enabled and the plugin version is below 3.1.2
  3. Review recent 2FA enrollment events
    Access WordPress activity logs or security logs. Look for 2FA enrollment/setup events within the plugin's logs or WordPress audit trail. Check for timestamps and user accounts involved.
    Affected if New 2FA enrollments appear that were not initiated by the legitimate account owner
  4. Inspect user accounts for bound email addresses
    Go to Users > All Users in WordPress admin. For each user with 2FA enabled (indicated by plugin status), examine the email address associated with their 2FA method. Compare against the user's registered WordPress email.
    Affected if A user's 2FA is bound to an email address that differs from their WordPress account email, indicating potential takeover
  5. Check authentication logs for 2FA bypass
    Review server access logs and WordPress authentication logs for successful logins where 2FA was satisfied but the email used for verification does not match the account owner.
    Affected if Logins show 2FA verification using an external email not associated with the legitimate user account

A user is affected if WP 2FA version is below 3.1.2 AND 2FA is enabled AND suspicious enrollment or account binding to unexpected emails is detected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP 2FA to version 3.1.2 or later. Until then, monitor for unauthorized 2FA enrollment events and consider disabling the plugin if not essential.

Recommended fix High confidence

WP 2FA version 3.1.1.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the WP 2FA plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.1.1.2 or later
  5. 5. Alternatively, manually download WP 2FA version 3.1.1.2 or later from the WordPress plugin repository and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12988 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data