CVE-2026-118202: Limit Login Attempts Security (WordPress plugin) · Improper Authentication
Affects Limit Login Attempts Security (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 3.4.1 soon.
Data as of 9 Nov 2026, 06:36 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 plugin to version 3.4.1 or later, where this vulnerability has been fixed. No other mitigation steps are indicated as the fix is available.
Description
The Limit Login Attempts Security WordPress plugin versions before 3.4.1 contains an improper authentication vulnerability. The plugin does not verify that the two-factor authentication step has succeeded before completing a login, treating failures in this step as successful authentication. This flaw allows an attacker who already knows a user's password to bypass the second factor by sending a specially crafted request header that disrupts the two-factor authentication process.