CVE-2026-127221 json
WPS Limit Login < 1.5.9.5 Brute Force via IPv6 Address Rotation
published 15h ago modified 14h ago also EUVD-2026-127370
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
WPS Limit Login (wps-limit-login) before 1.5.9.5 contains an improper access control vulnerability that allows unauthenticated attackers to bypass login lockout protections by keying the per-attempt login counter and lockout map on the raw, non-canonicalized IPv6 client address. Attackers controlling a routable IPv6 /64 prefix can send each login attempt from a fresh address within that range, preventing any counter from reaching the lockout threshold and enabling effectively unlimited brute-force password guessing against WordPress accounts.
Patch / fix
Is CVE-2026-127221 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- NicolasKulka WPS Limit Login
Classification
- Weakness
-
- CWE-307 Improper Restriction of Excessive Authentication Attempts
- Technology feeds
References
-
wordpress.org
/plugins/wps-limit-login/#developers
release-notes, patch
-
vulncheck.com
/advisories/wps-limit-login-brute-force-via-ipv6-address-rotation
third-party-advisory
Sources
- CVE List CVE-2026-127221
- NVD CVE-2026-127221
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.