HomeWordPress vulnerabilitiesLogin Lockdown & Protection
Login Lockdown & Protection vulnerabilities
Login Lockdown & Protection has 4 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 4
- Active installs
- 100,000+
- Latest version
- 2.17
- Last updated
- 16 Aug 2026
- Most recent
- 6 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Security weakness CVE-2026-97308 | Medium 4.8 | Up to 2.17 | No fixed version yet | 1 d ago |
| Security weakness CVE-2025-11707 | Medium 5.3 | Up to 2.14 | Fixed in a later version (latest 2.17) | 13 Dec 2025 |
| Broken access control CVE-2025-3766 | Medium 5.4 | Up to 2.11 | Fixed in a later version (latest 2.17) | 7 May 2025 |
| Broken access control CVE-2024-1340 | Medium 5.4 | Before 2.09 | Fixed in 2.09 | 29 Feb 2024 |
Read the published descriptions
- CVE-2026-97308, 6 Oct 2026
- Unauthenticated Bypass Vulnerability in Login Lockdown <= 2.17 versions. CVE record
- CVE-2025-11707, 13 Dec 2025
- The Login Lockdown & Protection plugin for WordPress is vulnerable to IP Block Bypass in all versions up to, and including, 2.14. This is due to $unblock_key key being insufficiently random allowing unauthenticated users, with access to an administrative user email, to generate valid unblock keys for their IP Address. This makes it possible for unauthenticated attackers to bypass blocks due to invalid login attempts. CVE record
- CVE-2025-3766, 7 May 2025
- The Login Lockdown & Protection plugin for WordPress is vulnerable to unauthorized nonce access due to a missing capability check on the ajax_run_tool function in all versions up to, and including, 2.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to obtain a valid nonce that can be used to generate a global unlock key, which can in turn be used to add arbitrary IP address to the plugin allowlist. This can only by exploited on new installations where the site administrator hasn't visited the loginlockdown page yet. CVE record
- CVE-2024-1340, 29 Feb 2024
- 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 record
What to do if you run Login Lockdown & Protection
If you run Login Lockdown & Protection, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Login Lockdown & Protection vulnerabilities
Free. We email you when a new vulnerability is published for Login Lockdown & Protection, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.