Skip to main content

WP 2FA CVE-2026-12988

| EUVDEUVD-2026-43628 MEDIUM
Missing Authorization (CWE-862)
2026-07-14 WPScan GHSA-ghqr-w463-c6wr
6.4
CVSS 3.1 · Vendor: WPScan
Share

Severity by source

Vendor (WPScan) PRIMARY
6.4 MEDIUM
AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
vuln.today AI
7.1 HIGH

Network attack requiring pre-compromised credentials (AC:H, PR:L); account takeover yields high confidentiality and integrity impact, not availability, correcting the provided vector's C:L/I:L/A:H miscalibration.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 14, 2026 - 13:25 vuln.today
CVSS changed
Jul 14, 2026 - 13:22 NVD
6.4 (MEDIUM)
Patch available
Jul 14, 2026 - 11:17 EUVD
CVE Published
Jul 14, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 14, 2026 - 06:00 cve.org
MEDIUM 6.4

DescriptionCVE.org

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.

AnalysisAI

Account takeover in the WP 2FA WordPress plugin (all versions before 3.1.1.2) is achievable by any attacker who has obtained a valid user's credentials. The plugin fails to verify that the email address submitted during two-factor authentication enrollment belongs to the authenticated account (CWE-862: Missing Authorization), allowing the attacker to redirect the setup verification code to an attacker-controlled inbox and complete 2FA enrollment on behalf of the victim. A publicly available proof-of-concept exists per WPScan; this vulnerability is not currently listed in the CISA KEV catalog, but the combination of a PoC, medium-prevalence deployment, and account-takeover impact warrants prompt patching.

Technical ContextAI

WP 2FA is a WordPress plugin that adds multi-factor authentication flows to WordPress sites. During the 2FA setup/enrollment phase, the plugin sends a verification code to an email address supplied by the initiating user. The root cause is CWE-862 (Missing Authorization): the plugin performs no ownership check to confirm that the user-supplied email matches the WordPress account's registered address. This is a server-side input validation failure on a security-critical enrollment endpoint. The affected product is identified by CPE cpe:2.3:a:unknown:wp_2fa:*:*:*:*:*:*:*:*, covering all versions up to but not including 3.1.1.2. Because the flaw sits in the enrollment flow rather than the verification step, it bypasses the intent of 2FA entirely - the very mechanism meant to protect accounts becomes the vector for takeover.

RemediationAI

Update the WP 2FA WordPress plugin to version 3.1.1.2 or later, which introduces proper ownership verification of the email address supplied during 2FA enrollment. This is a vendor-released patch and the fix version is confirmed by EUVD-2026-43628. The WPScan advisory at https://wpscan.com/vulnerability/8aa6bf91-54ee-4326-a477-31f42284be22/ provides additional remediation context. As a compensating control before patching, site administrators should enforce strong, unique passwords and enable login anomaly detection to reduce the likelihood of credential compromise - the mandatory prerequisite for this exploit. Disabling new 2FA enrollments at the plugin level, if the feature allows it, would eliminate the attack surface entirely until a patch is applied, though this prevents legitimate users from enrolling. Sites using SSO or external identity providers that bypass WP 2FA enrollment are not exposed via this specific flow.

Share

CVE-2026-12988 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy