Login Lockdown & Protection vulnerabilities
Plugin slug login-lockdown · 6 known vulnerabilities · latest disclosed 2026-10-05 · WordPress.org page
Every listed vulnerability has a fix. Version 2.18 or later is not affected by any of them. If your site runs an older version, update it.
1 of 6 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Login Lockdown & Protection
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 5.3 | <= 2.17 | 2.18 | CVE-2026-97308 | 2026-10-05 | Advisory |
| Medium 5.3 | <= 2.14 | 2.15 | CVE-2025-11707 | 2025-12-12 | Advisory |
| Medium 5.4 | <= 2.11 | 2.12 | CVE-2025-3766 | 2025-05-06 | Advisory |
| Medium 5.4 | <= 2.08 | 2.09 | CVE-2024-1340 | 2024-02-09 | Advisory |
| Medium 6.6 | < 2.07 | 2.07 | CVE-2023-50837 | 2023-12-21 | Advisory |
| High 7.2 | <= 2.06 | 2.07 | none | 2023-11-21 | Advisory |
Check if a site is affected
Enter a site address to see which version of Login Lockdown & Protection and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Login Lockdown & Protection plugin safe to use?
All 6 known issues are fixed in current versions (2.18 or later). Keeping it updated is what matters.
How do I check which version of Login Lockdown & Protection my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.