Login Lockdown – Protect Login Form: A security weakness

Login Lockdown – Protect Login Form is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 5.4 CVSS 3.1 · security@wordfence.com

NVD score Pending NVD has not published its own CVSS assessment.

Component: Login Lockdown – Protect Login Form
Plugin slug: login-lockdown
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Feb 29, 2024
Weakness: CWE-862 — Missing Authorization

This CVE was published Feb 29, 2024 and is one of 4 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Login Lockdown – Protect Login Form to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

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

References

Update, patch or deactivate.

Technical description

Primary and upstream sources