CVE-2026-18356: Limit Login Attempts Security (WordPress plugin) · Incomplete Blacklist
Affects Limit Login Attempts Security (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 3.3.5 when convenient.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.3.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 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 19 Nov 2026.
What to do
Upgrade Limit Login Attempts Security (WordPress plugin) to 3.3.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Limit Login Attempts Security | Affected
| Fixed in
|
AI-suggested
A fix is available in Limit Login Attempts Reloaded version 3.3.5. Users should upgrade to version 3.3.5 or later to address this vulnerability. No other mitigation steps are indicated.
Description
The Limit Login Attempts Reloaded WordPress plugin versions before 3.3.5 contains an incomplete blacklist vulnerability. The plugin's username denylist does not perform case-insensitive comparisons and does not consider the account's email address. This allows an account that an administrator intended to block from logging in to bypass the restriction and authenticate successfully.