WP 2FA <= 2.2.1 — Time-Based TOTP attack to Sensitive Information Exposure
CVE-2022-2891Published · Updated Action summary
Affected: ≤2.2.1Update to 2.3.0 or newer
All remediation steps- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:LConfidentiality- Low
I:NIntegrity- None
A:NAvailability- None
- Required access
- No account needed
- 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≤ 2.2.1
- Patched in2.3.0
Update to 2.3.0 or newer.
You are affected if you run ≤ 2.2.1. Version 2.3.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.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 2.3.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 Calvin Alkan.
The WP 2FA plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.2.1 due to the use of a linear-time comparison operator when comparing token hashes. This allows an attacker to gain information about authentication tokens by observing small time differences in server response times. This is a vulnerability that is generally not realistically exploitable over the internet due to other factors that will have a greater influence on response times.
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 | Two-Factor Authentication Bypass ≤4.0.0Update to 4.1.0 | CVE-2026-15372 | |
| Medium4.3 | Authenticated (Subscriber+) Account Takeover ≤3.1.1.1Update to 3.1.1.2 | CVE-2026-12988 |
- 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.3Two-Factor Authentication Bypass
≤4.0.0Update to 4.1.0
- Medium4.3Authenticated (Subscriber+) Account Takeover
≤3.1.1.1Update to 3.1.1.2
Timeline
CVE published
Severity medium, CVSS 5.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.