2FA <= 4.0.0 — Two-Factor Authentication Bypass
CVE-2026-15372Published · Updated Action summary
Affected: ≤4.0.0Update to 4.1.0 or newer
All remediation steps- Severity
- Medium4.3
- CVSS
- 4.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- Unknown
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
WP 2FA – Two-factor authentication for WordPress wp-2fa
- Affected≤ 4.0.0
- Patched in4.1.0
Update to 4.1.0 or newer.
You are affected if you run ≤ 4.0.0. Version 4.1.0 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP 2FA – Two-factor authentication for WordPress.
- No admin access? Run a passive check of your site. It reads public files only.
What to do
- Update to version 4.1.0, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch WP 2FA – Two-factor authentication for WordPress to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Jakub Herman.
The WP 2FA – Two-factor authentication for WordPress plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in all versions up to, and including, 4.0.0. This makes it possible for authenticated attackers, with Custom-level access and above, to bypass 2FA.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in WP 2FA – Two-factor authentication for WordPress
All 14| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Low2.7 | Authenticated (Administrator+) Insecure Direct Object Reference <4.2.0Update to 4.2.0 | CVE-2026-108066 | |
| Medium4.3 | Cross-Site Request Forgery ≤4.1.0Update to 4.2.0 | CVE-2026-62142 | |
| Medium4.3 | Unauthenticated Two-Factor Authentication Bypass ≤4.0.0Update to 4.1.0 | CVE-2026-103514 | |
| Medium4.3 | Authenticated (Subscriber+) Account Takeover ≤3.1.1.1Update to 3.1.1.2 | CVE-2026-12988 | |
| Medium5.3 | 2-Factor Authentication Bypass ≤2.9.3Update to 3.0.0 | CVE-2025-12628 |
- Low2.7Authenticated (Administrator+) Insecure Direct Object Reference
<4.2.0Update to 4.2.0
- Medium4.3Cross-Site Request Forgery
≤4.1.0Update to 4.2.0
- Medium4.3Unauthenticated Two-Factor Authentication Bypass
≤4.0.0Update to 4.1.0
- Medium4.3Authenticated (Subscriber+) Account Takeover
≤3.1.1.1Update to 3.1.1.2
- Medium5.32-Factor Authentication Bypass
≤2.9.3Update to 3.0.0
Timeline
CVE published
Severity medium, CVSS 4.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.