CVE-2026-111739: Two Factor Authentication (WordPress plugin) · Improper Authentication
Affects Two Factor Authentication (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 1.17.0 soon.
Data as of 29 Oct 2026, 07:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.17.0, 5.5.0
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 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 29 Oct 2026.
What to do
Upgrade Two Factor Authentication to 1.17.0; All-In-One Security (AIOS) to 5.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Two Factor Authentication | Affected
| Fixed in
|
| All-In-One Security (AIOS) | Affected
| Fixed in
|
AI-suggested
Upgrade the Two Factor Authentication WordPress plugin to version 1.17.0 or later and the All-In-One Security (AIOS) WordPress plugin to version 5.5.0 or later, where this vulnerability has been fixed.
Description
A vulnerability in the Two Factor Authentication WordPress plugin (before 1.17.0) and the All-In-One Security (AIOS) WordPress plugin (before 5.5.0) allows improper authentication. The flaw occurs because the plugins do not bind the two-factor authentication code to the account being authenticated. An attacker who knows a victim's password and has their own two-factor-enabled account can bypass the victim's second-factor check by using their own two-factor code, thereby gaining access to the victim's session.