The Limit Login Attempts Security WordPress plugin before 3.4.1 does not confirm that its two-factor authentication
Source GCVE Database
Not known to be exploited : upgrade to 3.4.1 soon.
Data as of 9 Nov 2026, 10:33 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 3.4.1
Exploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 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 8 Nov 2026.
What to do
Upgrade Limit Login Attempts Security (WordPress plugin) to 3.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Limit Login Attempts Security | Affected
| Fixed in
|
AI-suggested
Upgrade the Limit Login Attempts Security WordPress plugin to version 3.4.1 or later, where this vulnerability has been addressed. No other mitigation steps are indicated in the available data.
Description
The Limit Login Attempts Security WordPress plugin versions before 3.4.1 contains a vulnerability where the two-factor authentication (2FA) step is not properly confirmed before completing a login. This flaw allows an attacker who knows a user's password to bypass the second factor by sending a specially crafted request header that disrupts the 2FA process.