WEB-ART Creative Design

Web-Art Login Shield with reCAPTCHA is a focused security plugin that protects WordPress authentication, Elementor Login widgets and Elementor Forms against automated attacks.
It strengthens wp-login.php, Elementor Login and Elementor Forms by integrating Google reCAPTCHA v2 verification and optional IP-based rate limiting, without replacing or modifying WordPress core authentication logic.
The plugin is intentionally lightweight and transparent: 
– no ads 
– no telemetry or analytics sent to the author 
– no third-party dashboards provided by the plugin 
– no all-in-one security suite overhead
All login protection modules (reCAPTCHA, Login Protect, Advanced login URL) are opt-in and disabled by default.
Additionally, the plugin can apply a small XML-RPC hardening rule-set (disables a few high-risk XML-RPC methods) to reduce common abuse vectors. This does not disable XML-RPC completely. XML-RPC hardening is applied only when Login Protect is enabled and “Protect XML-RPC logins” is enabled.
Each module (reCAPTCHA, Login Protect, Advanced login URL) can be enabled independently. Elementor reCAPTCHA options require reCAPTCHA to be configured and verified.
<h3>Key Features</h3>
<h4>reCAPTCHA v2 integration</h4>
<ul>
<li>reCAPTCHA v2 checkbox for wp-login.php (when enabled and IP is not allowlisted)</li>
<li>server-side token verification for WordPress login and Elementor Forms validation</li>
<li>reCAPTCHA must be verified before enabling protection</li>
</ul>
<h4>Elementor reCAPTCHA options</h4>
<ul>
<li>automatic frontend injection for Elementor Login widgets (when enabled)</li>
<li>optional frontend injection for Elementor Forms (Elementor Pro) (when enabled)</li>
<li>Custom Alignment: Ability to set Left, Center, or Right alignment for reCAPTCHA in both Elementor Login and Elementor Forms directly from plugin settings.</li>
<li>Elementor frontend scripts inject reCAPTCHA only when they detect relevant widgets/forms in the DOM (supports dynamically loaded content, popups, AJAX, etc.)</li>
<li>Google reCAPTCHA scripts are not loaded for allowlisted IPs</li>
</ul>
<h4>Whitelist IPs (reCAPTCHA)</h4>
<ul>
<li>reCAPTCHA IP allowlist (allowlisted IPs bypass reCAPTCHA checks on wp-login.php, Elementor Login and Elementor Forms; Login Protect may still apply)</li>
<li>reCAPTCHA allowlist accepts one entry per line (exact IP match only)</li>
<li>optional note format supported: IP | reason (reason is ignored for matching)</li>
</ul>
<h4>Login Protect (IP-based lockouts)</h4>
<ul>
<li>failed login attempt counting per IP address</li>
<li>timed lockouts after a configurable threshold</li>
<li>blocked IP list (lockouts expire automatically after the configured lockout time)</li>
<li>recent security event log (stored locally)</li>
<li>wp-login.php lockout UX: countdown notice and temporary submit blocking during an active lockout</li>
<li>Login Protect is independent of reCAPTCHA (can be enabled and used without reCAPTCHA enabled)</li>
<li>three practical protection modes:
<ul>
<li>MODE 1 – reCAPTCHA only</li>
<li>MODE 2 – reCAPTCHA + Login Protect</li>
<li>MODE 3 – Login Protect only</li>
</ul>
</li>
</ul>
<h4>Trusted IPs (Login Protect)</h4>
<ul>
<li>separate allowlists for reCAPTCHA and Login Protect (exact IP match only)</li>
<li>Login Protect allowlist accepts one entry per line (exact IP match only)</li>
<li>optional note format supported: IP | reason (reason is ignored for matching)</li>
</ul>
<h4>REST API and XML-RPC protection (optional)</h4>
<ul>
<li>optional protection for authentication attempts via XML-RPC and REST API (applies only when the corresponding checkbox is enabled; Login Protect must be enabled)</li>
</ul>
<h4>XML-RPC hardening (optional)</h4>
<ul>
<li>optionally disables a small set of high-risk XML-RPC methods commonly abused by attackers:
<ul>
<li>pingback.ping</li>
<li>pingback.extensions.getPingbacks</li>
<li>system.multicall</li>
</ul>
</li>
<li>XML-RPC hardening is applied only when Login Protect is enabled and “Protect XML-RPC logins” is enabled 
This reduces abuse without disabling XML-RPC entirely.</li>
</ul>
<h4>Advanced login URL (optional)</h4>
<ul>
<li>single toggle enables Advanced login behavior</li>
<li>custom login endpoint (rewrites requests to the standard WordPress login handler without altering core authentication logic)</li>
<li>when Advanced is enabled, wp-login.php and wp-admin are protected for non-authenticated visitors</li>
<li>protection behavior is configured via two required fields:
<ul>
<li>Custom login URL slug (example: “secure-login-1234”)</li>
<li>Default redirect slug (recommended: “404” to display the active theme’s 404 page)</li>
</ul>
</li>
<li>both fields are required when Advanced is enabled (saving is blocked if any field is empty)</li>
<li>if fields are empty when enabling Advanced, the plugin auto-generates a secure random login slug and sets the redirect slug to the recommended default</li>
<li>protection applies only to non-authenticated users (logged-in users can still access wp-admin and wp-login.php)</li>
<li>safe fallback handling to avoid logout loops (wp-login.php?action=logout remains accessible)</li>
</ul>
<h4>IP Blocking (Site-wide)</h4>
<ul>
<li>single toggle enables site-wide IP blocking</li>
<li>permanently blocks selected IP addresses from accessing the entire site (returns HTTP 403)</li>
<li>blocklist accepts one entry per line (exact IP match only)</li>
<li>optional note format supported: IP | reason (reason is ignored for matching)</li>
<li>recommended use cases: persistent abuse, scraping, hostile bots, repeated attacks not covered by login-only protection</li>
<li>warning: do not add your own IP address unless you have alternative access (hosting panel / WP-CLI / database access) to remove the entry</li>
</ul>
<h3>Technical Design Principles</h3>
<ul>
<li>
Fail-closed security model (scoped) 
If reCAPTCHA verification cannot be completed and reCAPTCHA protection is enabled for the given login or form, the request is rejected to reduce the risk of automated bypass. 
Administrators can always regain access by disabling the feature in plugin settings or by deactivating the plugin via hosting or FTP.
</li>
<li>
Non-intrusive defaults 
Login protection modules remain disabled until explicitly enabled by an administrator.
</li>
<li>
Conflict awareness 
If another plugin injects reCAPTCHA into login or form flows, it should be disabled to avoid duplicate widgets or verification conflicts.
</li>
<li>
Emergency config kill-switches (wp-config.php) 
For recovery scenarios (e.g. accidental lockouts), selected modules can be force-disabled via wp-config.php constants. This does not bypass security rules; it disables the module logic before it runs. Remove the constant to restore normal behavior.
</li>
</ul>
<h3>External Services</h3>
This plugin integrates with Google reCAPTCHA v2, an external service provided by Google LLC.
reCAPTCHA features are disabled by default. The plugin does not load reCAPTCHA scripts or send verification requests unless an administrator enables reCAPTCHA protection and/or uses the “Verify reCAPTCHA” test in the plugin settings.
Google’s reCAPTCHA JavaScript (https://www.google.com/recaptcha/api.js) may be loaded on: 
– wp-login.php (when reCAPTCHA is enabled and the visitor IP is not allowlisted) 
– the frontend (when Elementor Login protection is enabled and a non-allowlisted visitor loads the page; injection occurs only if Elementor Login widgets are detected in the DOM) 
– the frontend (when Elementor Forms protection is enabled and a non-allowlisted visitor loads the page; injection occurs only for Elementor Forms) 
– the plugin settings page only when an administrator runs the “Verify reCAPTCHA” test (if provided in the UI)
When a visitor (or admin during verification) completes the reCAPTCHA challenge: 
– a verification token (g-recaptcha-response) is generated in the browser 
– during server-side verification on your website, the token and the configured Secret Key are sent to: 
 https://www.google.com/recaptcha/api/siteverify 
– the visitor’s IP address is sent to Google as the remoteip parameter when it is available on the server
The plugin sends the g-recaptcha-response token to Google only when the protected form is submitted (login attempt / form submission) or when an administrator runs the “Verify reCAPTCHA” test. 
The plugin does not send usernames, passwords, email addresses, or any form field contents to Google – only the reCAPTCHA token, the configured Secret Key, and the visitor IP address (remoteip) when available.
The plugin does not store or process any data returned by Google beyond the verification result, and it does not send any telemetry, analytics, or usage data to the plugin author.
Note: Google reCAPTCHA may set cookies and collect additional device and usage data in the visitor’s browser, as described in Google’s privacy policy and terms. Site owners are responsible for disclosing this in their site privacy policy and obtaining consent where required by applicable law.
Google privacy policies apply: 
– https://policies.google.com/privacy 
– https://policies.google.com/terms
<h3>Privacy</h3>
This plugin does not send telemetry, analytics or usage data to the plugin author or any third party.
Local data stored by the plugin (for security purposes only): 
– IP addresses related to login attempts / lockouts (Login Protect) 
– timestamps of failed attempts and lockouts 
– last username associated with a locked IP (Login Protect) 
– recent security event log entries (the plugin stores up to the last 30 events; entries rotate automatically) 
– last reCAPTCHA configuration or HTTP error (for admin diagnostics) 
– permanent site-wide IP blocklist entries (optional notes stored; notes are not used for matching)
Data retention: 
– security event log keeps only the most recent entries (up to 30; automatic rotation) 
– Login Protect state is stored locally and is automatically pruned (e.g. stale non-locked entries are removed over time and the list is capped) 
– permanent site-wide IP blocklist entries are retained until removed by an administrator 
– plugin data can be removed during uninstall if the uninstall cleanup option is enabled
All data is stored locally in the WordPress database and is used solely to enforce security rules and display administrative information.
<h3>Legal</h3>
reCAPTCHA is a trademark of Google LLC. 
Elementor is a trademark of Elementor Ltd. 
This plugin is not affiliated with, endorsed by, or sponsored by Google LLC or Elementor Ltd.

Web-Art Login Shield with reCAPTCHA

Protect WordPress logins and Elementor Login/Forms using Google reCAPTCHA v2 and optional IP-based lockouts.

Faiyaz Alam

Harm10

Leonardo Gandini

w3reign

The plugin helps you to track any visitor’s login details with the following attributes:
<ol>
<li>Login – Login Date-Time</li>
<li>Logout – Logout Date-Time</li>
<li>Last Seen – Last Seen Date-Time</li>
<li>Login Status – Logged in/Logged out/Failed</li>
<li>Online Status – Online/Offline/Idle</li>
<li>Session Duration – How long the user stayed on your website per session.</li>
<li>User ID</li>
<li>Username</li>
<li>Current Role</li>
<li>Old Role – The role while user gets logged in into your website.</li>
<li>Browser</li>
<li>Operating System</li>
<li>IP Address</li>
<li>Country Name and Country Code (Based on IP Address)</li>
<li>Timezone (Based on IP Address)</li>
<li>Mobile <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Whether the user loggedin with a mobile (e.g. tablet and mobile phone) device.</li>
<li>Proxy IP <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Whether the user loggedin from a proxy IP.</li>
</ol>
<h4>Features</h4>
The <a href="https://userloginhistory.com/" rel="nofollow ugc">User Login History Free Version</a> plugin has all the basic features that will help you to know your website visitors. The <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">User Login History Pro Version</a> plugin has some more premium and useful features along with all the basic features.
<ol>
<li>AUTO LOGOUT <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Automatically logout idle users every ‘X’ minute. 
You can also specify roles. 
This feature is built on WordPress Cron Job.</li>
<li>IP ADDRESS CONTROL <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Allows you to control of masking and hiding of user’s IP address.</li>
<li>EMAIL ALERT <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Allows you to get notified via email for success/failed login. 
You can also specify roles and modify email templates.</li>
<li>AUTO DELETE OLD RECORDS <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Automatically delete the records older than ‘X’ days. 
You can also specify the roles. 
This feature is built on WordPress Cron Job.</li>
<li>TRACK SPECIFIC ROLES <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Allows you to track specific roles only.</li>
<li>CSV SEPARATOR <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Allows you to enter a CSV separator for CSV export.</li>
<li>REPORT – TIMESHEET <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Generate a timesheet report</li>
<li>REPORT – NO LOGIN LIST <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Generate a report of users who have not login for a given date range</li>
<li>REPORT – LOGIN DEVICE <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a> – Generate report of login count based on IP address</li>
<li>LOGIN TIME TRACKER – Tracks the date and time of user’s login, logout, last seen, etc.</li>
<li>LOGIN STATUS TRACKER – Tracks user’s login status to check if the user is logged in, logged out, failed, etc.</li>
<li>ONLINE STATUS TRACKER – Tracks user’s online status to check if the user is online, idle or offline.</li>
<li>USER INFORMATION TRACKER – Tracks user’s old role, current role, username, etc.</li>
<li>DEVICE INFORMATION TRACKER – Tracks user’s operating system and browser.</li>
<li>GEO LOCATION TRACKER – Tracks user’s timezone and country based on IP address.</li>
<li>ADVANCED SEARCH FILTER – Filters the records.</li>
<li>CSV EXPORTER – Exports the records in csv format.</li>
<li>CUSTOMIZABLE SHORTCODE – Renders the records on front-end.</li>
<li>PREFERABLE TIMEZONE (DEPRECATED! Will be removed in 3.0) – You can select your preferred timezone to be used for the listing table.</li>
<li>MULTISITE NETWORK – On the network admin area, you can see the listing table which shows all the records fetched from all the blogs of the current network. </li>
</ol>
<h4>Translations</h4>
You can download the language files from <a href="https://translate.WordPress.org/projects/wp-plugins/user-login-history" title="Click here to download the language file for the plugin." rel="nofollow ugc">here</a>.
Do you want to translate this plugin to another language?
I recommend using <a href="http://poedit.net/" rel="nofollow ugc">POEdit</a> or if you prefer to do it straight from the WordPress admin interface use <a href="https://WordPress.org/plugins/loco-translate/" rel="ugc">Loco Translate</a>. 
When you’re done, post your file on this <a href="https://github.com/faiyazalam/WordPress-plugin-user-login-history/issues/6" rel="nofollow ugc">issue</a>. 
. 
You can also translate the plugin <a href="https://translate.WordPress.org/projects/wp-plugins/user-login-history" rel="nofollow ugc">online</a>.
<h4>How to use the plugin?</h4>
<ol>
<li>
To see all the tracked records in admin, click on the plugin menu shown in the left sidebar.
</li>
<li>
To see all the tracked records of current logged in users in frontend, use the following shortcode:
</li>
</ol>
Basic Usage of Shortcode:
In your template file:
<pre><code><?php echo do_shortcode('[user_login_history]'); ?>
</code></pre>
In your content:
<pre><code>[user_login_history]
</code></pre>
Advanced Usage of Shortcode:
In your template file:
<pre><code><?php echo do_shortcode("[user_login_history limit='20' reset_link='custom-uri' columns='ip_address,time_login' date_format='Y-m-d' time_format='H:i:s']"); ?>
</code></pre>
In your content:
<pre><code>[user_login_history limit='20' reset_link='custom-uri' columns='ip_address,time_login' date_format='Y-m-d' time_format='H:i:s']
</code></pre>
<h4>Shortcode Parameters</h4>
You can use the shortcode to display the login list of the current user. It does not display the login list of other users. 
Here is the list of all the parameters that you can use in the shortcode. All the parameters are optional.
<ol>
<li>
title – Title of the listing table. Default is: empty string
</li>
<li>
limit – Number of records per page. Default is: 20
</li>
<li>
reset_link – Custom URI of the listing page. For the input “my-login-history”, it will render a reset link with the following URL: 
www.example.com/my-login-history 
Default is the full permalink of the current post or page.
</li>
<li>
date_format – A valid date format. Default is:
Y-m-d
</li>
<li>
time_format – A valid time format. Default is:
H:i:s
</li>
<li>
show_timezone_selector – Whether you want to show timezone selector or not. Any value other than “true” will be treated as “false”. Default is: 
true
</li>
<li>
roles <a href="https://userloginhistory.com/features" title="View All Features" rel="nofollow ugc">(Pro Feature)</a>: 
It allows you to set role(s) in the shortcode parameter so that you can see the login list of other users who belong to the role(s).
[user_login_history roles=’administrator, editor’]
</li>
<li>
columns – List of column keys used to render columns on the listing table. Default keys are:
operating_system, browser, time_login, time_logout
</li>
<li>
Available Column Keys:
user_id, username, role, old_role, ip_address, country_name, browser, operating_system, timezone, user_agent, duration, time_last_seen, time_login, time_logout, login_status
</li>
</ol>
<h4>Geo Tracking</h4>
The plugin uses <a href="https://tools.keycdn.com/geo" rel="nofollow ugc">a free third party service</a> to detect country and timezone based on IP address. Many projects are using this free service due to which sometimes the server of the service provider becomes slow. This may affect the login functionality of your website. Hence it is recommended that you do not enable this functionality unless you have paid service or reliable service. If you have a paid service, you can <a href="https://userloginhistory.com/contact/" rel="nofollow ugc">contact us</a> to integrate it.
<h4>Login Statuses</h4>
<ol>
<li>
Logged in – If the user gets logged in successfully.
</li>
<li>
Logged out – If the user clicks on logout button and gets logged out successfully.
</li>
<li>
Failed – If the user enters invalid credentials.
</li>
<li>
Blocked (DEPRECATED! Will be removed in 3.0) – This is used for the multisite network. By default, a user can login to any blog and then WordPress redirects to the blog on which the user is associated. The plugin saves login info at the blog on which the user logged in but cannot not save the information of the blog on which WordPress redirects the user. You can prevent this behavior by using the plugin setting. Please note that we already removed this status from the pro version plugin but not from the free version yet.
</li>
<li>
Unknown (DEPRECATED! Will be removed in 3.0) – Since we have added a new column “Login Status” in the version 1.7.0, its value will be empty in the database table after upgrading to 1.7.0. To filter such records, you can use this status.
</li>
</ol>
Note – In case, a user log in with “Remember Me” and then closes his browser without doing logout, it will show the login status as “Logged in”.
<h4>Bug Fixes</h4>
If you find any bug, please create a topic with a step by step description to reproduce the bug. 
Please search the forum before creating a new topic.
<h4>Keywords</h4>
user log, log, logger, detector, tracker, membership, 
register, sign up, admin, subscriber, editor, contributor, geo location, 
profile, front end registration, manager, report, statistics, activity, user role editor

User Login History

Helps you to know your website's visitors by tracking their login related information like login/logout time, country, browser and many more.

Web-Art Login Shield with reCAPTCHA vs User Login History