CVE-2026-127220: Kadence Security (WordPress plugin) · Improper Restriction of Excessive Authentication Attempts
Affects Kadence Security (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 10.0.6.1 when convenient.
Data as of 17 Nov 2026, 19:36 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
- Patch
- Available – fixed in 10.0.6.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 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 16 Nov 2026.
What to do
Upgrade Kadence Security (WordPress plugin) to 10.0.6.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NexcessKadence Security – Password, Two Factor Authentication, and Brute Force Protection | Affected
| Fixed in
|
AI-suggested
A fixed version 10.0.6.1 of the Kadence Security plugin is available that addresses this vulnerability. Users should upgrade to version 10.0.6.1 or later to remediate this issue. No additional mitigation steps are required once the plugin is updated.
Description
The Kadence Security plugin for WordPress before version 10.0.6.1 contains a vulnerability that allows unauthenticated attackers to bypass brute-force protection by exploiting how IPv6 addresses are handled. The plugin keys failed-login counters on the full 128-bit IPv6 address rather than the /64 prefix, enabling attackers controlling a routed IPv6 /64 to reset counters by rotating addresses within that prefix. This allows password spraying and username enumeration attacks, as well as evasion of immediate admin bans via address rotation.