WordPress security by component
WP 2FA
Plugin description
WP 2FA is a WordPress component with 9 published CVE records in this archive. The latest tracked vulnerability was published Jul 14, 2026; the highest CVE/CNA score is 7.1.
Plugin slug:
wp-2faLatest vulnerability
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.
| Safe version |
|
||
|---|---|---|---|
| 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.
|
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.
|
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.
|
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.
|
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.
|
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.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Jan 11, 2024 |
CVE-2023-6506
WP 2FA – Two-factor authentication for: A security weakness
WP 2FA – Two-factor authentication for 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.
|
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.
|
See mitigation notes |
CVE5.9
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.
|
See mitigation notes |
CVE6.1
NVD6.1
|