WP 2FA: A security weakness
WP 2FA is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 3.1.1.2.
- Component
- WP 2FA
- Plugin slug
wp-2fa- Affected
- < 3.1.1.2
- Safe version
3.1.1.2- Published
- Jul 14, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jul 14, 2026 and is one of 9 known issues for this plugin.
Update, patch or deactivate.
Update WP 2FA to 3.1.1.2 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H