Description
Login Guard addresses the most common WordPress attack of all: automated password guessing against /wp-login.php.
- Rate limiting: locks an IP address out after too many failed attempts, for a configurable duration.
- Login history (7 days): every attempt with a pseudonymous fingerprint instead of the raw IP address, success or failure, and the user name tried (only readable if the account exists).
- Generic error messages: never reveals whether a user name exists.
- Safe allowlist behaviour: an IP address from which someone with administrator rights recently signed in successfully is only locked out after ten times the usual number of failed attempts, so a few typos never lock you out.
- Disable XML-RPC: closes the known bypass of rate limiting via system.multicall.
- Protection against user name enumeration (?author= parameter, the public REST user list, the author sitemap and oEmbed responses).
- Two-factor authentication (TOTP) for administrators, set up in the profile, with backup codes and a QR code generated locally.
- Optional check of new passwords against the Pwned Passwords list of Have I Been Pwned (only the first five characters of a hash are sent, never the password).
- “Security at a glance”: one box with the checks of all active 360 Orbit security plugins.
- Your active sessions in the profile: every browser you are signed in with, with device, shortened address, sign-in time and last activity; sign out a single one.
- Approve new registrations by hand: accounts that people create themselves cannot sign in until an administrator approves them; email to the administrator and to the user, approve or reject in the user list.
- Comment spam: an invisible trap field and a time check in the comment form move comments from bots to spam (nothing is deleted).
- A notice when an account shows its username as public name above posts and comments.
- Hidden trap field in the login form: bots that fill in every field are rejected, whatever the password is.
- A notice if an account is called admin, administrator or test, because attackers try these names first.
- Export and import of all settings as JSON, to set up several sites the same way.
- WP-CLI: inspect the status and unlock IP addresses even when wp-admin itself is unreachable.
Free version vs. Pro
The free version is complete on its own: rate limiting, login history, generic error messages, XML-RPC and enumeration protection, two-factor authentication for administrators, the leaked password check, and settings export/import.
Login Guard Pro adds:
- Two-factor authentication for every account, required per role with a grace period, after which the dashboard only opens the setup.
- Passkeys: sign in without a password using a fingerprint, face, device PIN or security key.
- A custom login URL instead of /wp-login.php, with a 404 for the real address.
- Notification when an account signs in from an unknown device.
- Trusted browsers: optionally skip the two-factor code in a browser for 7, 14 or 30 days; the password is always required.
- REST API only for signed-in users, with an allow list for forms, shops and embeds.
- A Sessions tab with all signed-in users: sign out one user or all others at once, and sign out after inactivity per role (an open admin tab alone does not count as activity).
- A fixed allow/block list for IP addresses and networks (CIDR).
- Automatic update notifications directly in the WordPress admin.
Login Guard Pro is a separate plugin available from the author; it is not required to use the free version.
External services
This plugin can connect to one external service, and only if you switch it on. After activation alone, and after an update, it contacts no server.
Pwned Passwords (Have I Been Pwned)
Used to check whether a password appears in known data breaches. Nothing is sent unless you tick “Reject passwords that appear in known data breaches” under Login Guard → Settings.
What is sent, and when:
- When someone sets a new password (profile, new user, password reset) and when an administrator signs in: the first five characters of the SHA-1 hash of the password, to
https://api.pwnedpasswords.com/range/. The password itself and the rest of the hash never leave your server; the service answers with all hash endings that start with these five characters, and the comparison happens on your server (k-anonymity). The request asks for padded answers, so even the size of the answer reveals nothing. - No user name, email address or website address is sent.
The service is provided by Have I Been Pwned: terms of use, privacy policy.
Installation
- Upload the plugin ZIP under Plugins → Add New → Upload Plugin, or install it from the plugin directory.
- Activate the plugin.
- Open the Login Guard menu and review the defaults under “Settings” (they already suit most sites).
FAQ
Can I lock myself out?
This is exactly the scenario the safety net protects against: an IP address from which a person with administrator rights recently signed in successfully is only locked out after ten times the usual number of failed attempts. In addition, every lockout can be lifted with one click under “Status & Lockouts”, and if wp-admin is unreachable, via WP-CLI (wp 360-orbit-login-guard unlock <ip>).
Are raw IP addresses stored?
No. The login history only stores a pseudonymous fingerprint (a hash of the IP address and a secret random value generated by the plugin). The plugin does not send any data to external services.
What happens on deactivation?
Rate limiting and all other protections stop immediately and the daily clean-up cron job is unscheduled. The existing login history and all settings are kept and are back immediately after reactivation. Only “Delete” in the plugin list removes them permanently.
Which languages does the admin interface support?
The admin interface follows the language configured in WordPress. Translations are delivered as WordPress.org language packs (translate.wordpress.org, text domain 360-orbit-login-guard); German is maintained by the author. You are welcome to contribute further languages there.
Screenshots
Changelog
1.0.39
- New: approve new registrations by hand. Accounts that people create themselves cannot sign in until an administrator approves them in the user list.
1.0.38
- New: your active sessions in the profile, each one can be signed out.
- New: comment spam check with an invisible trap field and a time check.
- New: a notice when an account shows its username as public name.
- The Pro version gains a Sessions tab with sign-out after inactivity, trusted browsers for two-factor and an option to keep the REST API for signed-in users.
1.0.37
- Changed: the “Security at a glance” box no longer mentions other plugins that are not installed.
1.0.36
- Changed: the 360 WP Orbit overview shows the important boxes of the active plugins at the top, optionally also on the WordPress dashboard; all boxes and tables now use one width.
1.0.35
- Maintenance release for the free version; the Pro version remembers known devices for the new device email.
1.0.34
- New: two-factor authentication (TOTP) for administrators is now part of the free version, set up in the profile.
- New: optional check of passwords against known data breaches (Pwned Passwords, k-anonymity).
- New: user name protection also removes the author from oEmbed responses.
- New: “Security at a glance” box on the Status tab.
1.0.33
- Maintenance release for the free version; the Pro version gains a setup assistant.
1.0.32
- New: Quickstart on the Status tab applies the recommended settings in one click (also
wp 360-orbit-login-guard quickstart). Allow and block lists, the login address and two-factor stay untouched.
1.0.31
- Maintenance release.
1.0.30
- Maintenance release.
1.0.29
- Changed: the settings are split into groups with a submenu; saving always stores all groups.
- Changed: buttons, the License tab and Export/Import now look the same in all plugins of the suite (primary actions in the plugin colour, cards side by side).
1.0.28
- New: the texts of the plugin appear in German by default, also on sites in another language; under 360 WP Orbit > Overview the language can be switched to the language of the website. The WordPress.org package follows the language of the website and now ships the German translation itself, so no language pack is needed.
1.0.27
- Fix: custom login URL no longer shows “Undefined variable $user_login” and “$error” warnings on the login form.
1.0.26
- New: custom login URL shows the full address as a bookmarkable link with a copy button.
1.0.25
- Fix: blocked login requests return HTTP 404 instead of a fatal error when the theme has no readable 404 template.
1.0.24
- Changed: tab order as in the other 360 Orbit plugins: Settings, then Export/Import, then License (or the Pro tab) at the end.
- Changed: content boxes are 960 px wide as in the other 360 Orbit plugins and the License tab.
1.0.23
- Changed: settings use the WordPress settings page layout: one row per setting, rate limiting values in their own rows with units, checkboxes with descriptive labels.
- Changed: Login History has the same width as the other tabs; the import file field sits in its own row with the Import button below.
- Changed: License tab uses the same layout; disconnecting has its own danger zone.
1.0.22
- Updated: German translation completed (privacy policy text, personal data export, reverse proxy note, license server notice).
1.0.21
- Changed: the 360 WP Orbit overview now picks up new suite plugins automatically, as every plugin registers itself. No more list to keep in sync.
1.0.20
- New: the plugin list now shows a “Settings” link for this plugin, as it already does for the other plugins of the suite.
1.0.19
- The brand name “360 WP Orbit” is no longer offered for translation, as it is the same in every language.
1.0.18
- New: hidden trap field in the login form (on by default, can be switched off in the settings). Bots that fill in every field are rejected whatever the password is; the attempt counts as a failed login.
- New: a notice on the Status tab if an account is named admin, administrator or test.
1.0.17
- The 360 WP Orbit overview now also lists the new plugin 360 Orbit Database Cleaner.
1.0.16
- Fix: the 360 WP Orbit overview page could show the wrong name, link and description for one of the plugins (a duplicated list key). The list is now correct.
1.0.15
- Internal: texts of the Orbit overview page are now translatable instead of hard-coded German.
1.0.14
- Changed: the update screen in wp-admin now shows the plugin icon and banner (Pro only; the free version contains no updater).
1.0.13
- Fix: the help text in wp-admin claimed that an administrator is never locked out from an address they recently signed in from; since 1.0.12 this holds up to ten times the usual number of failed attempts.
1.0.12
- Security: “Trust the X-Forwarded-For header” now only reads the header when the request itself comes from an internal address or from a proxy you list with the
wp360_lg_trusted_proxiesfilter (single addresses or ranges such as 203.0.113.0/24). Behind a CDN with public addresses, add its ranges to that filter; otherwise the header is ignored. Before, anyone who could reach the server directly could fake the header and get around the rate limit. - Security: the exemption for a person’s own address is no longer unlimited. It applies up to ten times the failed-attempt limit, so someone sharing that address can no longer guess the password without end.
- Security: an account lock now lasts at most 15 minutes and only exists for real accounts, which limits locking other people out on purpose.
- Security: “Lost your password?” counts requests for existing and non-existing accounts the same way, so the lock message no longer shows which accounts exist.
- Privacy: names that are not an account (often a password typed into the wrong field) are no longer stored in readable form in the sign-in history. A suggested privacy policy text, data export and data erasure for the history were added.
- Changed: corrected plugin logo — lettering and symbol are now centered, the orbit is a closed ring.
- Fix: unlocking an address or account also forgets its failed attempts, so the next typo does not lock it again at once.
- Fix: successful Application Password requests are recorded at most once per hour, and expired locks are no longer listed.
1.0.11
- Fix: the German translation is now also used for Austrian, Swiss and formal German (de_AT, de_CH, de_DE_formal and so on).
1.0.10
- Fix: the one-time data migration from older versions no longer removes old settings if copying them failed, and it retries hourly until every step succeeded. A missing data table is created again. Uninstalling now also removes data left from older versions.


