WP 2FA at a glance
- 14 publicly disclosed vulnerabilities. The most recent was disclosed on Oct 14, 2026.
- Ranked #341 by popularity on WordPress.org (100,000+ active installs).
- The latest version is 4.3.0 (released Nov 10, 2026). The most recent security fix shipped in 4.2.0.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your WP 2FA version
Enter the WP 2FA version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “WP 2FA”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “WP 2FA”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (4.3.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known WP 2FA vulnerabilities
WP 2FA – Two-factor authentication for WordPress < 4.2.0 - Authenticated (Administrator+) Insecure Direct Object Reference
Missing authorization · CVE-2026-108066
Affected versions: < 4.2.0
Fixed in: 4.2.0
Severity: Low 2.7 · Disclosed Oct 14, 2026
WP 2FA – Two-factor authentication for WordPress <= 4.1.0 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2026-62142
Affected versions: ≤ 4.1.0
Fixed in: 4.2.0
Severity: Medium 4.3 · Disclosed Oct 8, 2026
2FA <= 4.0.0 - Unauthenticated Two-Factor Authentication Bypass
Missing authorization · CVE-2026-103514
Affected versions: ≤ 4.0.0
Fixed in: 4.1.0
Severity: Medium 4.3 · Disclosed Oct 1, 2026
2FA <= 4.0.0 - Two-Factor Authentication Bypass
Missing authorization · CVE-2026-15372
Affected versions: ≤ 4.0.0
Fixed in: 4.1.0
Severity: Medium 4.3 · Disclosed Jul 29, 2026
WP 2FA <= 3.1.1.1 - Authenticated (Subscriber+) Account Takeover
Missing authorization · CVE-2026-12988
Affected versions: ≤ 3.1.1.1
Fixed in: 3.1.1.2
Severity: Medium 4.3 · Disclosed Jun 23, 2026
WP 2FA – Two-factor authentication for WordPress <= 2.9.3 - 2-Factor Authentication Bypass
Missing authorization · CVE-2025-12628
Affected versions: ≤ 2.9.3
Fixed in: 3.0.0
Severity: Medium 5.3 · Disclosed Nov 3, 2025
WP 2FA <= 2.6.3 - Unauthenticated Information Exposure via Log File
Information disclosure · CVE-2022-44587
Affected versions: ≤ 2.6.3
Fixed in: 2.6.4
Severity: Medium 5.3 · Disclosed Jun 20, 2024
WP 2FA – Two-factor authentication for WordPress <= 2.6.2 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-32568
Affected versions: ≤ 2.6.2
Fixed in: 2.6.3
Severity: Medium 6.1 · Disclosed Apr 16, 2024
WP 2FA – Two-factor authentication for WordPress <= 2.5.0 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2023-6520
Affected versions: ≤ 2.5.0
Fixed in: 2.6.0
Severity: Medium 4.3 · Disclosed Jan 2, 2024
WP 2FA <= 2.5.0 - Insecure Direct Object Reference to Arbitrary Email Sending
Missing authorization · CVE-2023-6506
Affected versions: ≤ 2.5.0
Fixed in: 2.6.0
Severity: Medium 4.3 · Disclosed Jan 2, 2024
WP 2FA – Two-factor authentication for WordPress <= 2.2.0 - Missing Authorization
Missing authorization · CVE-2022-44595
Affected versions: ≤ 2.2.0
Fixed in: 2.2.1
Severity: Medium 4.3 · Disclosed Dec 7, 2022
WP 2FA <= 2.2.1 - Time-Based TOTP attack to Sensitive Information Exposure
Information disclosure · CVE-2022-2891
Affected versions: ≤ 2.2.1
Fixed in: 2.3.0
Severity: Medium 5.3 · Disclosed Sep 14, 2022
WP 2FA – Two-factor authentication for WordPress <= 2.2.0 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2022-1527
Affected versions: ≤ 2.2.0
Fixed in: 2.2.1
Severity: Medium 6.1 · Disclosed May 6, 2022
WP 2FA – Two-factor authentication for WordPress <= 2.1.0 - Insecure Direct Object Reference
Missing authorization
Affected versions: ≤ 2.1.0
Fixed in: 2.2.0
Severity: Medium 5.4 · Disclosed Apr 13, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| WP 2FA – Two-factor authentication for WordPress < 4.2.0 - Authenticated (Administrator+) Insecure Direct Object ReferenceMissing authorization · CVE-2026-108066 | < 4.2.0 | 4.2.0 | Low 2.7 | Oct 14, 2026 |
| WP 2FA – Two-factor authentication for WordPress <= 4.1.0 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2026-62142 | ≤ 4.1.0 | 4.2.0 | Medium 4.3 | Oct 8, 2026 |
| 2FA <= 4.0.0 - Unauthenticated Two-Factor Authentication BypassMissing authorization · CVE-2026-103514 | ≤ 4.0.0 | 4.1.0 | Medium 4.3 | Oct 1, 2026 |
| 2FA <= 4.0.0 - Two-Factor Authentication BypassMissing authorization · CVE-2026-15372 | ≤ 4.0.0 | 4.1.0 | Medium 4.3 | Jul 29, 2026 |
| WP 2FA <= 3.1.1.1 - Authenticated (Subscriber+) Account TakeoverMissing authorization · CVE-2026-12988 | ≤ 3.1.1.1 | 3.1.1.2 | Medium 4.3 | Jun 23, 2026 |
| WP 2FA – Two-factor authentication for WordPress <= 2.9.3 - 2-Factor Authentication BypassMissing authorization · CVE-2025-12628 | ≤ 2.9.3 | 3.0.0 | Medium 5.3 | Nov 3, 2025 |
| WP 2FA <= 2.6.3 - Unauthenticated Information Exposure via Log FileInformation disclosure · CVE-2022-44587 | ≤ 2.6.3 | 2.6.4 | Medium 5.3 | Jun 20, 2024 |
| WP 2FA – Two-factor authentication for WordPress <= 2.6.2 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-32568 | ≤ 2.6.2 | 2.6.3 | Medium 6.1 | Apr 16, 2024 |
| WP 2FA – Two-factor authentication for WordPress <= 2.5.0 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2023-6520 | ≤ 2.5.0 | 2.6.0 | Medium 4.3 | Jan 2, 2024 |
| WP 2FA <= 2.5.0 - Insecure Direct Object Reference to Arbitrary Email SendingMissing authorization · CVE-2023-6506 | ≤ 2.5.0 | 2.6.0 | Medium 4.3 | Jan 2, 2024 |
| WP 2FA – Two-factor authentication for WordPress <= 2.2.0 - Missing AuthorizationMissing authorization · CVE-2022-44595 | ≤ 2.2.0 | 2.2.1 | Medium 4.3 | Dec 7, 2022 |
| WP 2FA <= 2.2.1 - Time-Based TOTP attack to Sensitive Information ExposureInformation disclosure · CVE-2022-2891 | ≤ 2.2.1 | 2.3.0 | Medium 5.3 | Sep 14, 2022 |
| WP 2FA – Two-factor authentication for WordPress <= 2.2.0 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2022-1527 | ≤ 2.2.0 | 2.2.1 | Medium 6.1 | May 6, 2022 |
| WP 2FA – Two-factor authentication for WordPress <= 2.1.0 - Insecure Direct Object ReferenceMissing authorization | ≤ 2.1.0 | 2.2.0 | Medium 5.4 | Apr 13, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 14, 2026.
Most common weaknesses in WP 2FA
Missing authorization
8 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site request forgery (CSRF)
2 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Information disclosure
2 issues
Data that should stay private, such as user details or configuration values, can be read from outside.
Frequently asked questions
Is WP 2FA safe to use?
WP 2FA is a well-known plugin with 100,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.3.0) and turn on automatic updates.
How do I find which version of WP 2FA my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.