CVE-2026-11883: WebAuthn Provider for Two Factor (WordPress plugin) · Improper Authentication
Affects WebAuthn Provider for Two Factor (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High : upgrade to 2.5.6 soon.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.6
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade WebAuthn Provider for Two Factor (WordPress plugin) to 2.5.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WebAuthn Provider for Two Factor | Affected
| Fixed in
|
AI-suggested
A fix is available in version 2.5.6 of the WebAuthn Provider for Two Factor plugin. Users should upgrade to version 2.5.6 or later to remediate this vulnerability. Patch status is not explicitly confirmed in the vendor advisory, so verify with the plugin vendor for official remediation guidance.
Description
The WebAuthn Provider for Two Factor WordPress plugin before 2.5.6 does not correctly validate the second-factor authentication response, allowing an attacker who already knows a user's password to bypass the two-factor authentication requirement by submitting a malformed request.