CVE-2026-108066

WP 2FA – Two-factor authentication for WordPress < 4.2.0 - Authenticated (Administrator+) Insecure Direct Object Reference

2026-10-14 00:00
Muni Nitish Kumar Yaddala

Strategic Overview

Status
Patched in 4.2.0
Affected Plugin
WP 2FA – Two-factor authentication for WordPress
Affected Version
< 4.2.0
CVSS
2.7Low
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-108066
View all WP 2FA – Two-factor authentication for WordPress vulnerabilities

At a glance

CVE-2026-108066 is a low-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP 2FA WordPress plugin, affecting versions < 4.2.0. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 4.2.0; sites on affected versions should update now. Disclosed October 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The WP 2FA – Two-factor authentication for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to 4.2.0. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with administrator-level access and above, to perform an unauthorized action.

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 < 4.2.0 takes an account at Administrator level or above. 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 4.2.0: builds < 4.2.0 are affected, anything from 4.2.0 onward is not.

Remediation

Update to version 4.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 4.2.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-108066https://www.wordfence.com/threat-intel/vulnerabilities/id/2f9a783a-8495-4410-b350-4b8299880a64https://nvd.nist.gov/vuln/detail/CVE-2026-108066

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C