Limit Login Attempts
limit-login-attempts · plugin
Known security vulnerabilities for Limit Login Attempts. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
1 critical · 2 exploitable without logging in · 1 with no official fix seen · latest May 2, 2023
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- Last updated Apr 4, 2023: not updated for more than two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.7.2 · last updated Apr 4, 2023 · 200K+ installs
Not updated since Apr 4, 2023. A component left without updates for over two years should not be expected to patch new vulnerabilities.
wordpress.org status checked on Nov 19, 2026
Vulnerabilities
- Critical 9.8
CVE-2012-10001unauthenticated
The Limit Login Attempts plugin before 1.7.1 for WordPress does not clear auth cookies upon a lockout, which might make it easier for remote
- Medium 6.1
CVE-2023-1912unauthenticated≤ 1.7.1
Limit Login Attempts <= 1.7.1 - Unauthenticated Stored Cross-Site Scripting
- Medium 5.4
CVE-2023-1861subscriber+no fix seen
Limit Login Attempts < 1.7.2 - Subscriber+ Stored XSS
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (1.7.2) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.