Limit Login Attempts Reloaded vulnerability records, with lockout, list and 2FA checks
This plugin limits login attempts, and the titles of its records include ones ending "Login Rate Limiting Bypass" and "Unauthenticated Username Denylist Bypass".
Match your version to each record, then read the lockout numbers, the Safelist and Denylist, the 2FA roles and who can see the lockout log.
On this page
Limit Login Attempts Reloaded vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 6 records for Limit Login Attempts Reloaded. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 3.4.2
Worked out from data retrieved on .
Every affected range listed in this source for Limit Login Attempts Reloaded ends before version 3.4.2.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Limit Login Attempts Security - Brute Force Protection, 2FA, Firewall & Login Security < 3.4.2 - Authenticated (Administrator+) Server-Side Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.5)
- CVE:
- CVE-2026-118439
Affected versions- All versions before 3.4.2
Patched versions: 3.4.2
Update to at least version 3.4.2.
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention < 3.3.5 - Unauthenticated Username Denylist Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-18356
Affected versions- All versions before 3.3.5
Patched versions: 3.3.5
Update to at least version 3.3.5.
Limit Login Attempts Reloaded <= 2.25.26 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2023-6934
Affected versions- All versions up to and including 2.25.26
Patched versions: 2.25.27
Update to at least version 2.25.27.
Limit Login Attempts Reloaded <= 2.25.25 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2023-5525
Affected versions- All versions up to and including 2.25.25
Patched versions: 2.25.26
Update to at least version 2.25.26.
Limit Login Attempts Reloaded <= 2.17.3 - Login Rate Limiting Bypass
- Published:
- Last updated:
- Severity:
- High (CVSS 7.3)
- CVE:
- CVE-2020-35590
Affected versions- All versions up to and including 2.17.3
Patched versions: 2.17.4
Update to at least version 2.17.4.
Show 1 older recordHide the older record
Limit Login Attempts Reloaded <= 2.15.2 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2020-35589
Affected versions- All versions up to and including 2.15.2
Patched versions: 2.17.4
Update to at least version 2.17.4.
Check Limit Login Attempts Reloaded on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Limit Login Attempts Reloaded counts, and where its settings are typed
Limit Login Attempts Reloaded is published on WordPress.org by WPChef, on a listing whose heading begins Limit Login Attempts Security.
Its free-version features include limiting login attempts by IP address and username, built-in two-factor authentication, failed login attempt logs, and safelist and denylist support for IPs and for usernames. Its FAQ lists the URLs being protected as the login page (wp-login.php, wp-admin), xmlrpc.php, the WooCommerce login page and any custom login page that uses regular WordPress login hooks.
Input arrives from two sides. Whoever submits one of those forms supplies a username and an address: the vendor's Active Lockouts Log page defines its Login column as the username that was used in the attack. The rest is typed into the plugin's own screens: lockout numbers on Settings, lists on Logs, roles under 2FA Settings.
The Settings tab text also gives a shortcode, llar-link, for inserting links into a GDPR message that it says will appear at the bottom of the login page.
WordPress's roles page says an Administrator has access to all administration features within a single site. The changelog file's entry for 2.26.13 reads: New "llar_admin" capability added to let other roles access the plugin. Count both when listing who can open the plugin's screens.
Limit Login Attempts Reloaded security records, filed under two names
The titles quoted here begin "Limit Login Attempts Reloaded" or "Limit Login Attempts Security".
The listing carries the second name, the vendor's documentation site is headed Limit Login Attempts Reloaded Software Docs, and the Settings tab text says the LLAR plugin. Match on the version fields, not on the name in a title.
Two of those titles end in Bypass. CVE-2020-35590 has a title ending "Login Rate Limiting Bypass" (affected: all versions up to and including 2.17.3; patched: 2.17.4). CVE-2026-18356 has a title ending "Unauthenticated Username Denylist Bypass" (affected: all versions before 3.3.5; patched: 3.3.5).
Two more end in Cross-Site Scripting. CVE-2023-6934 has a title ending "Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode" (affected: all versions up to and including 2.25.26; patched: 2.25.27). CVE-2020-35589 has a title ending "Reflected Cross-Site Scripting" (affected: all versions up to and including 2.15.2; patched: 2.17.4).
That range ends short of its patched version. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
Five read-only checks on the Settings tab, the Logs tab and 2FA Settings
All five can be done by reading, on a site you are authorised to review, so leave every screen without pressing Save Settings.
Vendor pages give two routes to the plugin: the activation page says to click Settings in the left-hand menu and select Limit Login Attempts, and the two-factor page says to go to Limit Login Attempts > 2FA Settings. The changelog file's entry for 3.0.2 says the plugin redirects to Dashboard when setup is incomplete and a tab other than Dashboard is opened.
If that happens, record it and ask the site owner before going further: completing setup is a change, not a reading.
On the Plugins screen, look for the row under either name the record titles use. WordPress's documentation says the Description column includes the version number and that an update notice is displayed when the Plugin Directory holds a newer version. Note both, and what the Automatic update column shows.
The changelog on the plugin's WordPress.org listing marks some entries "Security:" in the vendor's own words, so read it before relying on the update guidance at the top of the history, because a release the vendor marks that way may have no record in the feed this page uses.
The vendor's page on max login attempts says to open the Settings tab and scroll to App Settings, where a free user uses the Local App section and a premium user the Limit Login Attempts Reloaded Cloud App section. It says the allowed retries field under Lockout is set to 4 by default.
The Settings tab's own text has four lines under Lockout: allowed retries, minutes lockout, lockouts increase lockout time to a number of hours, and hours until retries are reset. Write down every number, and copy the Trusted IP Origins field as it stands: its help text says the vendor strongly recommends not using anything other than REMOTE_ADDR.
Note which app is active too. The vendor's active-app page says the app will downgrade to Local until the following month if a premium plan's resources are exceeded, so on a premium site copy both sections.
For the free version, the vendor's safelist page says to open the Logs tab, where boxes for Safelist and Denylist sit right under Statistics; for premium users it says the lists are called IP Access Rules and Login Access Rules. The local Logs tab's text labels two boxes under each list, one for an IP or IP range per line and one for a username per line.
Copy every line. The changelog file's entry for 3.3.3 reads: Allowed safelisted usernames (matched case-insensitively, including by email) to bypass lockouts and the MFA prompt on login.
So ask whose each safelisted entry is, and why it is there. The tab's text also has buttons labelled Reset Counter, Restore Lockouts, Clear Log and Unlock. Press none of them.
The vendor's two-factor page says that under 2FA Settings you check the option to enable multi-factor authentication and select the user roles required to use it. Record whether Enable 2FA is ticked and which boxes are ticked under User Roles, both that screen's own labels, then compare them with the Role column on the Users screen.
The changelog file's entry for 3.2.1 says that when no user groups are selected, 2FA stays disabled. The screen's text says 2FA is available with email only. Copy any notice it shows, such as one in its text that reads: 2FA is temporarily disabled via rescue link.
It will be automatically re-enabled in 1 hour. The two-factor page calls rescue links one-time use backup links, so ask where the site's copies are kept, and do not generate new ones.
The vendor's IP Logs page puts the Event Logs on the Logs tab, and its Active Lockouts Log page calls them a log of all login attempts for the website. The local Logs tab's text labels a Lockout log with the columns Date, IP, Tried to log in as and Gateway.
Start the list of readers with every Administrator, using the role filter links on the Users screen, then ask the site's developer whether any other role holds llar_admin. Record where lockout information goes besides that tab. The Settings tab text has a Notify on lockout setting with an email address to which lockout notifications will be sent: record the address and whose inbox it is.
The listing's premium features include CSV exports of login and IP activity and cloud backups of IP security data, so on a premium site record who holds the cloud account.
What a version match cannot read: the Safelist, the 2FA roles and the active app
A version outside every affected range in the history says nothing about the numbers typed under Lockout, a username on the Safelist, a 2FA Settings screen with no role selected, or which app is active.
A version inside a range shows exposure to a known record, not whether anyone used a flaw while that version was installed.
A WordPress security audit measures the behaviour itself. It sends a measured run of failed logins to wp-login.php and xmlrpc.php, two of the URLs the listing's FAQ names, and records whether, and when, each starts refusing them. It also compares the error text and timing for a real and an invented username.
Frequently asked questions
It depends on the record. CVE-2023-5525, whose title ends "Missing Authorization", lists all versions up to and including 2.25.25, with 2.25.26 in its patched versions field. CVE-2020-35590 lists all versions up to and including 2.17.3. Compare your installed version with every affected range in the history on this page, then read the update guidance at the top of the history.
The records on this page are the ones the source data files under the WordPress.org slug limit-login-attempts-reloaded, and the listing at that address has a heading that begins Limit Login Attempts Security. The same listing has a section on upgrading from the original Limit Login Attempts plugin, which the changelog file calls the ancestor plugin. The fields here cannot show whether a record also applies to that one.
The records are those the source data files under this plugin's slug, and being filed there does not settle the paid edition. The vendor's activation page says the premium version is activated with a special setup code sent via email once the subscription is paid for, and the Settings tab text describes its Active App setting as switching from free version (local) to premium (cloud).
The text of the 2FA Settings screen says enabling the feature sends limited data to an endpoint at limitloginattempts.com to process 2FA authentication. It says the data may include the site domain, user ID (if known), username, a partially hidden email address, IP addresses, user role (if known) and browser and device information, and that passwords are never transmitted.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Limit Login Attempts Security - Brute Force Protection, 2FA, Firewall & Login Security < 3.4.2 - Authenticated (Administrator+) Server-Side Request Forgery (CVE-2026-118439)
- Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention < 3.3.5 - Unauthenticated Username Denylist Bypass (CVE-2026-18356)
- Limit Login Attempts Reloaded <= 2.25.26 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (CVE-2023-6934)
- Limit Login Attempts Reloaded <= 2.25.25 - Missing Authorization (CVE-2023-5525)
- Limit Login Attempts Reloaded <= 2.17.3 - Login Rate Limiting Bypass (CVE-2020-35590)
- Limit Login Attempts Reloaded <= 2.15.2 - Reflected Cross-Site Scripting (CVE-2020-35589)