WP 2FA – Two-factor authentication for WordPress <= 2.1.0 - Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 2.2.0
- Affected Plugin
- WP 2FA – Two-factor authentication for WordPress
- Affected Version
<= 2.1.0- CVSS
- 5.4Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE pending
At a glance
This record tracks a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP 2FA WordPress plugin, affecting versions <= 2.1.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.2.0; sites on affected versions should update now. Disclosed April 2022, reported by Maycon Vitali.
Vulnerability Overview
The WP 2FA – Two-factor authentication for WordPress plugin for WordPress make it possible for attackers to disable other user's 2FA settings in versions up to, and including, 2.1.0.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in WP 2FA <= 2.1.0 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP 2FA the fix is 2.2.0: builds <= 2.1.0 are affected, anything from 2.2.0 onward is not.
Remediation
Update to version 2.2.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP 2FA 2.2.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP 2FA – Two-factor authentication for WordPress
- 6.1CVE-2024-32568: WP 2FA Reflected XSS
CVE-2024-32568 - 6.1CVE-2022-1527: WP 2FA Reflected XSS
CVE-2022-1527 - 5.3CVE-2025-12628: WP 2FA 2-Factor Authentication Bypass
CVE-2025-12628 - 5.3CVE-2022-44587: WP 2FA <= 2.6.3 Information Exposure
CVE-2022-44587 - 5.3CVE-2022-2891: WP 2FA <= 2.2.1 Time-Based TOTP attack to Info Exposure
CVE-2022-2891 - 4.3CVE-2026-12988: WP 2FA <= 3.1.1.1 Account Takeover
CVE-2026-12988 - 4.3CVE-2023-6520: WP 2FA – Two-factor authentication for WordPress CSRF
CVE-2023-6520 - 4.3CVE-2022-44595: WP 2FA Missing Authorization
CVE-2022-44595
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C