CVE-2026-12988: WP 2FA account takeover via email binding in setup wizard

CVE-2026-12988 · Severity: info · CVSS 6.4 · Published 2026-07-14

A vulnerability in the WP 2FA plugin for WordPress allows attackers to hijack the two-factor authentication (2FA) setup process. If an attacker gains a user's password, they can complete the 2FA enrollment using their own email address instead of the user's. This results in a full account takeover, locking the legitimate owner out of their account and requiring administrative intervention to restore access.

Vendors: Melapress.

Quick answers

Is CVE-2026-12988 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-12988 being exploited in the wild.
How severe is CVE-2026-12988?
Informational severity, with a CVSS score of 6.4, published 14 July 2026.
Which products and versions are affected?
Melapress WP 2FA < 3.1.1.2.
Is there a fix for CVE-2026-12988?
A patch was published on 2026-07-14: Fixed in version 3.1.1.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-12988 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-12988?
Check whether you run Melapress WP 2FA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The WP 2FA plugin fails to validate the email address provided during the initial 2FA enrollment wizard against the user's registered account email. An attacker who has obtained a user's primary credentials (e.g., via phishing or credential stuffing) can log in and, if the account has not yet completed 2FA setup, intercept the setup process. By sending a crafted AJAX request to 'send_authentication_setup_email' with an attacker-controlled email address, the attacker can receive the verification code, complete enrollment, and bind the account's 2FA to their own mailbox. This bypasses intended restrictions where codes should only be sent to the registered user's email. The issue is fixed in version 3.1.1.2.

Affected products

  • Melapress WP 2FA < 3.1.1.2

Timeline

  • 2026-06-23: disclosed: Original researcher disclosure
  • 2026-07-14: advisory: NVD and WPScan advisory published
  • 2026-07-14: patched: Fixed in version 3.1.1.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.