Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-1340: CWE-862 Missing Authorization in webfactory Login Lockdown – Protect Login Form

0
Medium
VulnerabilityCVE-2024-1340cvecve-2024-1340cwe-862
Published: Tue Feb 20 2024 (02/20/2024, 18:56:25 UTC)
Source: CVE Database V5
Vendor/Project: webfactory
Product: Login Lockdown – Protect Login Form

Description

CVE-2024-1340 is a medium-severity vulnerability in the WordPress plugin 'Login Lockdown – Protect Login Form' (all versions up to 2. 08). It arises from a missing authorization check in the generate_export_file function, allowing authenticated users with subscriber-level access or higher to export sensitive plugin settings. These settings include whitelisted IP addresses and a global unlock key. An attacker possessing the global unlock key can add their IP to the whitelist, bypassing login restrictions. Exploitation requires authentication but no user interaction beyond login. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or mitigating access to prevent unauthorized privilege escalation and potential bypass of login protections.

AI-Powered Analysis

AILast updated: 02/26/2026, 09:26:28 UTC

Technical Analysis

The vulnerability identified as CVE-2024-1340 affects the WordPress plugin 'Login Lockdown – Protect Login Form' developed by webfactory. This plugin is designed to enhance login security by restricting access based on IP whitelisting and locking down login attempts. The flaw lies in the generate_export_file function, which lacks proper authorization checks (CWE-862: Missing Authorization). Consequently, any authenticated user with at least subscriber privileges can invoke this function to export the plugin's configuration data. Exported data includes sensitive information such as the list of whitelisted IP addresses and a global unlock key. Possession of the global unlock key enables an attacker to add their own IP address to the whitelist, effectively circumventing login restrictions and potentially gaining persistent unauthorized access. The vulnerability affects all plugin versions up to and including 2.08. The CVSS 3.1 base score is 5.4 (medium), reflecting that exploitation requires network access and authenticated privileges but no user interaction, and results in limited confidentiality and integrity impact without affecting availability. No public exploits have been reported yet, but the vulnerability presents a significant risk in environments where subscriber-level accounts are easily obtainable or compromised. The absence of patch links suggests that a fix may not yet be available, emphasizing the need for immediate mitigation steps.

Potential Impact

This vulnerability allows attackers with low-level authenticated access to escalate their privileges indirectly by exporting sensitive plugin settings and manipulating the IP whitelist. The impact includes unauthorized bypass of login restrictions, which can lead to further unauthorized access to the WordPress admin panel or other protected resources. Confidentiality is impacted as sensitive configuration data is exposed, and integrity is affected because attackers can alter whitelist entries. Although availability is not directly impacted, the breach of login controls can facilitate subsequent attacks such as brute force, data theft, or site defacement. Organizations relying on this plugin for login security may face increased risk of account compromise, especially if subscriber accounts are not tightly controlled. This can affect website integrity, user trust, and potentially lead to broader network compromise if the WordPress site is part of a larger infrastructure.

Mitigation Recommendations

1. Immediately restrict subscriber and low-privilege user access to trusted individuals only until a patch is available. 2. Monitor and audit user activities, especially export operations related to the plugin. 3. If feasible, temporarily disable or uninstall the 'Login Lockdown – Protect Login Form' plugin until an official patch is released. 4. Implement additional access controls at the web server or firewall level to limit access to the WordPress admin area. 5. Use strong, unique credentials and enforce multi-factor authentication (MFA) for all authenticated users to reduce the risk of account compromise. 6. Regularly review and update IP whitelists manually to detect unauthorized additions. 7. Stay informed on vendor updates and apply patches promptly once available. 8. Consider alternative plugins with verified secure authorization checks for login protection if patching is delayed.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-02-07T21:35:00.199Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6d2bb7ef31ef0b56e8f2

Added to database: 2/25/2026, 9:44:11 PM

Last enriched: 2/26/2026, 9:26:28 AM

Last updated: 2/26/2026, 11:07:45 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats