Plugins · two-factor-2fa-via-email · data as of 2026-11-04
Is Two Factor (2FA) Authentication via Email safe? Known vulnerabilities and latest version
- Latest version
- 1.9.12
- Last updated
- 2026-10-21
- Active installs
- 9,000+
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 5.6+
Enable one-click login with this WordPress Two-Factor Authentication (2FA) plugin, utilizing email for added security. — by Sully
What to do
- Update to the latest version (1.9.12). Anything older than 1.9.9 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get two-factor-2fa-via-email --field=version shows what you run; wp plugin update two-factor-2fa-via-email updates it.
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.5 CVE-2025-13587 · published 2026-02-19
Authentication bypass in Two Factor (2FA) Authentication via Email (1.9.8 and older)
- Affected
- 1.9.8 and older
- Fixed in
- 1.9.9 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2025-13587Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-10-21 — latest release on wordpress.org (1.9.12).
- 2026-02-19 — Authentication bypass disclosed (CVE-2025-13587), fixed in 1.9.9.
Get an email when Two Factor (2FA) Authentication via Email has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Two Factor (2FA) Authentication via Email (two-factor-2fa-via-email) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Sully (2 tracked)
Types found in this plugin: Authentication bypass (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/two-factor-2fa-via-email (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/two-factor-2fa-via-email"><img src="https://laskyr.com/plugins/two-factor-2fa-via-email/badge.svg" alt="Two Factor (2FA) Authentication via Email vulnerability status"></a>