Two Factor (2FA) Authentication via Email: Privilege escalation or authentication bypass
Two Factor (2FA) Authentication via Email is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess.
- Component
- Two Factor (2FA) Authentication via Email
- Plugin slug
two-factor-2fa-via-email- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Feb 19, 2026
This CVE was published Feb 19, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Two Factor (2FA) Authentication via Email to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
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 Two Factor (2FA) Authentication via Email plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 1.9.8. This is because the SS88_2FAVE::wp_login() method only enforces the 2FA requirement if the 'token' HTTP GET parameter is undefined, which makes it possible to bypass two-factor authentication by supplying any value in the 'token' parameter during login, including an empty one.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N