Login Lockdown & Protection <= 2.17 — Unauthenticated Login Lockout Protection Bypass
CVE-2026-97308Published · Updated Action summary
Affected: ≤2.17Update to 2.18 or newer
All remediation steps- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
Login Lockdown & Protection login-lockdown
- Affected≤ 2.17
- Patched in2.18
Update to 2.18 or newer.
You are affected if you run ≤ 2.17. Version 2.18 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Login Lockdown & Protection.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 2.18, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Login Lockdown & Protection to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Ananda Dhakal.
The Login Lockdown & Protection plugin for WordPress is vulnerable to Bypass Vulnerability in all versions up to, and including, 2.17. This is due to the is_rest_request() function trusting the user-supplied $_GET['rest_route'] parameter to determine whether a request is a REST API call, allowing any unauthenticated request to masquerade as a REST request and skip lockout enforcement. This makes it possible for unauthenticated attackers to bypass the login lockout protection entirely by supplying a crafted `rest_route` GET parameter, allowing unlimited login attempts regardless of configured lockout thresholds.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Login Lockdown & Protection
All 6| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | IP Block Bypass ≤2.14Update to 2.15 | CVE-2025-11707 | |
| Medium5.4 | Missing Authorization to Authenticated (Subscriber+) Arbitrary IP Whitelisting ≤2.11Update to 2.12 | CVE-2025-3766 | |
| Medium5.4 | Missing Authorization ≤2.08Update to 2.09 | CVE-2024-1340 | |
| Medium6.6 | Authenticated(Administrator+) SQL Injection <2.07Update to 2.07 | CVE-2023-50837 | |
| High7.2 | Authenticated (Administrator+) SQL Injection ≤2.06Update to 2.07 | — |
- Medium5.3IP Block Bypass
≤2.14Update to 2.15
- Medium5.4Missing Authorization to Authenticated (Subscriber+) Arbitrary IP Whitelisting
≤2.11Update to 2.12
- Medium5.4Missing Authorization
≤2.08Update to 2.09
- Medium6.6Authenticated(Administrator+) SQL Injection
<2.07Update to 2.07
- High7.2Authenticated (Administrator+) SQL Injection
≤2.06Update to 2.07
Timeline
CVE published
Severity medium, CVSS 5.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.