CVE-2026-12988
Deferred Deferred - Pending Action

WP 2FA Authentication Email Spoofing Vulnerability

Vulnerability report for CVE-2026-12988, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-14

Assigner: WPScan

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-14
Generated
2026-08-03
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-02
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wp_2fa wp_2fa to 3.1.1.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-12988 is a vulnerability in the WP 2FA WordPress plugin versions before 3.1.1.2. The plugin fails to verify that the email address provided during the two-factor authentication (2FA) setup process belongs to the user configuring it.

An attacker who has already obtained a user's credentials can exploit this flaw by redirecting the 2FA setup verification code to an email address they control. This allows the attacker to complete the 2FA setup for the victim's account, effectively taking over the account.

Once the attacker has set up 2FA with their own email, the victim may be locked out of their account because credential recovery would require passing the 2FA challenge, which is now controlled by the attacker.

  • The vulnerability is classified under OWASP A5: Broken Access Control (CWE-862).
  • The attack requires the victim to be within the 2FA enrollment grace period and not permitted to specify a custom email address for 2FA.
Detection Guidance

Detecting this vulnerability requires checking the version of the WP 2FA plugin installed on your WordPress site. The vulnerability affects versions prior to 3.1.1.2.

  • Check the plugin version via the WordPress admin dashboard: Navigate to 'Plugins' and look for 'WP 2FA' in the list. The version number will be displayed.
  • Alternatively, you can check the plugin version by inspecting the plugin directory on the server. Run the following command in the terminal: cat /path/to/wordpress/wp-content/plugins/wp-2fa/readme.txt | grep 'Stable tag'.
  • Review user accounts that are in the 2FA enrollment grace period. If users are permitted to specify a custom email address for 2FA setup, this could indicate a potential misconfiguration or vulnerability.

There are no specific network-based detection methods for this vulnerability, as it is a logic flaw in the plugin's 2FA setup process.

Impact Analysis

If you are using an affected version of the WP 2FA plugin (before 3.1.1.2), this vulnerability could allow an attacker to take over your WordPress account.

  • An attacker who has your credentials can bypass 2FA by redirecting the verification code to their own email, locking you out of your account.
  • Once the attacker controls your account, they may perform unauthorized actions, such as modifying content, accessing sensitive data, or installing malicious plugins.
  • Account recovery becomes difficult because the attacker now controls the 2FA process, making it harder for you to regain access.
Compliance Impact

This vulnerability could impact compliance with several standards and regulations, depending on the nature of the data and systems involved.

  • GDPR: If the compromised account has access to personal data of EU citizens, this vulnerability could lead to a data breach. GDPR requires organizations to implement appropriate security measures, including multi-factor authentication, to protect personal data. A failure to secure accounts properly could result in non-compliance and potential fines.
  • HIPAA: For organizations handling protected health information (PHI), this vulnerability could lead to unauthorized access to sensitive patient data. HIPAA requires covered entities to implement access controls and authentication mechanisms to protect PHI. A breach resulting from this vulnerability could violate HIPAA's Security Rule.
  • Other standards: This vulnerability may also affect compliance with frameworks like PCI DSS (for payment data), ISO 27001 (information security management), or NIST guidelines, which require strong authentication mechanisms to protect sensitive data and systems.

Organizations should assess whether this vulnerability exposes them to risks of non-compliance and take corrective actions, such as updating the plugin or implementing additional security controls.

Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Update the WP 2FA plugin to version 3.1.1.2 or later. This version contains the fix for the vulnerability.
  • If updating is not immediately possible, disable the WP 2FA plugin until the update can be applied. This will prevent attackers from exploiting the flaw.
  • Review user accounts that have recently set up 2FA. Ensure that the email addresses used for 2FA verification belong to the legitimate users and not to an attacker.
  • Enforce strict access controls and monitor for suspicious activity, such as unexpected 2FA setup requests or changes to email addresses associated with accounts.
  • Educate users about the risks of phishing attacks, as obtaining user credentials is a prerequisite for exploiting this vulnerability.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12988. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart