Skip to main content
Menu
CVEs

CVE

Nexcess Kadence Security login lockout bypass via IPv6 address rotation

CVE-2026-127220EUVD-2026-127200GHSA-H8P5-HVM5-X47W

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 10.0.6.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 10.0.6.1.

Published
Last modified
Reference
Last checked
27/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

The Kadence Security plugin for WordPress tracks failed logins per full IPv6 address, which lets a remote attacker who doesn't need to log in evade per-host lockouts. By sending each attempt from a new address within a routed IPv6 /64 range, an attacker can keep resetting the counter to carry out password spraying and username enumeration.

Written by a model from the sources below. Verify against them.

Original description

Kadence Security plugin for WordPress (better-wp-security) before 10.0.6.1 contains a brute-force protection bypass vulnerability that allows unauthenticated attackers to evade per-host login lockouts by exploiting IPv6 address handling in ITSEC_Lib::get_ip(), which keys failed-login counters on the full 128-bit IPv6 address rather than a /64 prefix. Attackers who control a routed IPv6 /64 can send each login attempt from a new address within that prefix, resetting the per-host counter each time to perform password spraying and username enumeration, and can similarly evade the auto_ban_admin immediate ban via address rotation.

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 10.0.6.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-127220 (Kadence Security WordPress Plugin < 10.0.6.1 IPv6 Lockout Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-127220 (entry last updated 2026-11-17):
Affected:
- Nexcess Kadence Security – Password, Two Factor Authentication, and Brute Force Protection: fixed in 10.0.6.1
Fixed versions: 10.0.6.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127220 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127220 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://wordpress.org/plugins/better-wp-security/#developers
- https://www.vulncheck.com/advisories/kadence-security-wordpress-plugin-ipv6-lockout-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-127220
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127220"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • Nexcess Kadence Security – Password, Two Factor Authentication, and Brute Force Protection

    fixed in 10.0.6.1

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Patch
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-127220

Is CVE-2026-127220 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-127220?

Kadence Security – Password, Two Factor Authentication, and Brute Force Protection: before 10.0.6.1.Source: cve.now feed data

How do I fix CVE-2026-127220?

Upgrade to a fixed version: 10.0.6.1.Source: cve.now feed data

More CVEs