WebAuthn Provider for Two Factor <= 2.5.5 - Two-Factor Authentication Bypass
Strategic Overview
- Status
- Patched in 2.5.6
- Affected Plugin
- WebAuthn Provider for Two Factor
- Affected Version
<= 2.5.5- CVSS
- 5.3Medium
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-11883
At a glance
CVE-2026-11883 is a medium-severity Improper Authentication vulnerability in the WebAuthn Provider for Two Factor WordPress plugin, affecting versions <= 2.5.5. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.6; sites on affected versions should update now. Disclosed June 2026, reported by Volodymyr Kolesnykov.
Vulnerability Overview
The WebAuthn Provider for Two Factor plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in all versions up to, and including, 2.5.5. This makes it possible for unauthenticated attackers to bypass 2FA when enabled for accounts.
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 privileges on the target site, and no interaction from a victim user.
CWE-287: Improper Authentication
Reaching this weakness in WebAuthn Provider for Two Factor <= 2.5.5 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For WebAuthn Provider for Two Factor the fix is 2.5.6: builds <= 2.5.5 are affected, anything from 2.5.6 onward is not.
Remediation
Update to version 2.5.6, 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: WebAuthn Provider for Two Factor 2.5.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C