WordPress security by component
WP 2FA
WP 2FA (wp-2fa) is a WordPress plugin with 10 published CVE records in this archive. The latest tracked vulnerability was published Aug 05, 2026; the highest published CVSS base score is 7.5.
Plugin slug:
wp-2faLatest vulnerability
CVE-2026-15372: WP 2FA login method permits second-factor bypass
WP 2FA before 4.1.0 fails to validate the second factor when one supported authentication method is selected during login. An attacker who already knows the target's WordPress password can choose the affected method, bypass two-factor verification and obtain the full user session, including an administrator session. This unscored record received deeper review because it is an authentication-bypass primitive. The CNA does not disclose the affected method, login action or request parameter.
| Safe version |
|
||
|---|---|---|---|
| Aug 05, 2026 |
CVE-2026-15372
WP 2FA login method permits second-factor bypass
WP 2FA before 4.1.0 fails to validate the second factor when one supported authentication method is selected during login. An attacker who already knows the target's WordPress password can choose the affected method, bypass two-factor verification and obtain the full user session, including an administrator session. This unscored record received deeper review because it is an authentication-bypass primitive. The CNA does not disclose the affected method, login action or request parameter.
|
4.1.0 |
CVE7.5
NVDPending
|
| Jul 14, 2026 |
CVE-2026-12988
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. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
3.1.1.2 |
CVE6.4
NVDPending
|
| Nov 24, 2025 |
CVE-2025-12628
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 public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE6.3
NVDPending
|
| Jun 21, 2024 |
CVE-2022-44587
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 public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.3
NVD7.5
|
| Apr 18, 2024 |
CVE-2024-32568
WP 2FA: Cross-site scripting
WP 2FA is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE7.1
NVD6.1
|
| Mar 21, 2024 |
CVE-2022-44595
WP 2FA: Privilege escalation or authentication bypass
WP 2FA 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. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.3
NVD5.3
|
| Jan 11, 2024 |
CVE-2023-6520
WP 2FA – Two-factor authentication for: Cross-site request forgery
WP 2FA – Two-factor authentication for is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Jan 11, 2024 |
CVE-2023-6506
WP 2FA – Two-factor authentication for: Broken access control
WP 2FA – Two-factor authentication for is affected by broken access control. Exposure depends on how the affected operation is made reachable by the site. A successful request can reach data or an operation that should be restricted to another user or a more privileged role. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Oct 10, 2022 |
CVE-2022-2891
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 public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVEPending
NVD5.9
|
| May 30, 2022 |
CVE-2022-1527
WP 2FA: Cross-site scripting
WP 2FA is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVEPending
NVD6.1
|