CVE-2026-97308

Login Lockdown & Protection <= 2.17 - Unauthenticated Login Lockout Protection Bypass

2026-10-05 00:00

Strategic Overview

Status: Patched in 2.18
Affected Plugin: Login Lockdown & Protection
Affected Version: <= 2.17
CVSS: 5.3Medium
Weakness type: CWE-693 · Protection Mechanism Failure
CVE: CVE-2026-97308

View all Login Lockdown & Protection vulnerabilities

At a glance

CVE-2026-97308 is a medium-severity Protection Mechanism Failure vulnerability in the Login Lockdown & Protection WordPress plugin, affecting versions <= 2.17. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.18; sites on affected versions should update now. Disclosed October 2026, reported by Ananda Dhakal.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-693: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Remediation

Update to version 2.18, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Login Lockdown & Protection 2.18 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-97308 https://www.wordfence.com/threat-intel/vulnerabilities/id/d4723d9e-9b37-4a1f-ad40-47a918018184 https://nvd.nist.gov/vuln/detail/CVE-2026-97308

Related records

Other vulnerabilities in Login Lockdown & Protection

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/