HomeWordPress vulnerabilitiesWP 2FA
WP 2FA vulnerabilities
WP 2FA has 8 known vulnerabilities in this database. The most recent published record is dated 3 Oct 2026.
- Known vulnerabilities
- 8
- Active installs
- 100,000+
- Latest version
- 4.1.0
- Last updated
- 11 Aug 2026
- Most recent
- 3 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Authentication bypass CVE-2026-103514 | High 7.5 | Before 4.1.0 | Fixed in 4.1.0 | 4 d ago |
| Authentication bypass CVE-2026-15372 | High 7.5 | Before 4.1.0 | Fixed in 4.1.0 | 5 Aug 2026 |
| Broken access control CVE-2026-12988 | Medium 6.4 | Before 3.1.1.2 | Fixed in 3.1.1.2 | 14 Jul 2026 |
| Security weakness CVE-2025-12628 | Medium 6.3 | Not yet published | Check for an update | 24 Nov 2025 |
| Cross-site request forgery (CSRF) CVE-2023-6520 | Medium 4.3 | Before 2.6.0 | Fixed in 2.6.0 | 11 Jan 2024 |
| Broken access control CVE-2023-6506 | Medium 4.3 | Up to 2.5.0 | Fixed in a later version (latest 4.1.0) | 11 Jan 2024 |
| Security weakness CVE-2022-2891 | Medium 5.9 | Before 2.3.0 | Fixed in 2.3.0 | 10 Oct 2022 |
| Cross-site scripting (XSS) CVE-2022-1527 | Medium 6.1 | Before 2.2.1 | Fixed in 2.2.1 | 30 May 2022 |
Read the published descriptions
- CVE-2026-103514, 3 Oct 2026
- The WP 2FA WordPress plugin before 4.1.0 does not invalidate a time-based one-time passcode once it has been used, allowing an attacker who knows an account's password and has observed a valid code within its validity window to replay it and bypass two-factor authentication, including on administrator accounts. CVE record
- CVE-2026-15372, 5 Aug 2026
- The WP 2FA WordPress plugin before 4.1.0 does not validate the second authentication factor when one of its supported methods is selected at login, allowing an attacker who already knows a user's password to bypass two-factor authentication and fully access the account, including administrator accounts. CVE record
- CVE-2026-12988, 14 Jul 2026
- 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 record
- CVE-2025-12628, 24 Nov 2025
- The WP 2FA WordPress plugin does not generate backup codes with enough entropy, which could allow attackers to bypass the second factor by brute forcing them CVE record
- CVE-2023-6520, 11 Jan 2024
- The WP 2FA - Two-factor authentication for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.5.0. This is due to missing or incorrect nonce validation on the send_backup_codes_email function. This makes it possible for unauthenticated attackers to send emails with arbitrary content to registered users via a forged request granted they can trick a site administrator or other registered user into performing an action such as clicking on a link. While a nonce check is present, it is only executed if a nonce is set. By omitting a nonce from the request, the check can be bypassed. CVE record
- CVE-2023-6506, 11 Jan 2024
- The WP 2FA - Two-factor authentication for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.5.0 via the send_backup_codes_email due to missing validation on a user controlled key. This makes it possible for subscriber-level attackers to email arbitrary users on the site. CVE record
- CVE-2022-2891, 10 Oct 2022
- The WP 2FA WordPress plugin before 2.3.0 uses comparison operators that don't mitigate time-based attacks, which could be abused to leak information about the authentication codes being compared. CVE record
- CVE-2022-1527, 30 May 2022
- The WP 2FA WordPress plugin before 2.2.1 does not sanitise and escape a parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting CVE record
What to do if you run WP 2FA
If you run WP 2FA, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP 2FA vulnerabilities
Free. We email you when a new vulnerability is published for WP 2FA, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.