# CVE-2026-127220: Kadence Security WordPress Plugin < 10.0.6.1 IPv6 Lockout Bypass


- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-h8p5-hvm5-x47w

## What is CVE-2026-127220?

CVE-2026-127220 is a medium-severity vulnerability in Nexcess Kadence Security – Password, Two Factor Authentication, and Brute Force Protection, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-127220?


## How do I fix CVE-2026-127220?

No fix has been published for CVE-2026-127220 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127220 being exploited?

There is no known exploitation of CVE-2026-127220 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127220 and fix it if it is affected.

What it is: CVE-2026-127220 is a medium-severity vulnerability in Nexcess Kadence Security – Password, Two Factor Authentication, and Brute Force Protection, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127220 in the wild and no public exploit code.

Affected product: Nexcess Kadence Security – Password, Two Factor Authentication, and Brute Force Protection. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127220/ (Markdown: https://insights.sbomify.com/CVE-2026-127220/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127220
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127220
- OSV: https://osv.dev/vulnerability/CVE-2026-127220

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127220/
Summaries are generated and may contain mistakes; the official description above is the record.
