Login Lockdown – Protect Login Form <= 2.08 - Missing Authorization
Strategic Overview
- Status
- Patched in 2.09
- Affected Plugin
- Login Lockdown & Protection
- Affected Version
<= 2.08- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-1340
At a glance
CVE-2024-1340 is a medium-severity Missing Authorization vulnerability in the Login Lockdown & Protection WordPress plugin, affecting versions <= 2.08. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.09; sites on affected versions should update now. Disclosed February 2024, reported by Lucio Sá.
Vulnerability Overview
The Login Lockdown – Protect Login Form plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the generate_export_file function in all versions up to, and including, 2.08. This makes it possible for authenticated attackers, with subscriber access and higher, to export this plugin's settings that include whitelisted IP addresses as well as a global unlock key. With the global unlock key an attacker can add their IP address to the whitelist.
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 interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Login Lockdown & Protection <= 2.08 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Login Lockdown & Protection the fix is 2.09: builds <= 2.08 are affected, anything from 2.09 onward is not.
Remediation
Update to version 2.09, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Login Lockdown & Protection 2.09 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Login Lockdown & Protection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C