Description
🇫🇷 Fully translated into French. Interface et documentation intégralement disponibles en français.
Twelve security modules. One lightweight plugin. No premium tier.
Login Armor protects WordPress login, accounts and administration with twelve independent modules. It is built for agencies, freelancers and site owners who want practical security, clear evidence and safe defaults without a remote dashboard, bundled telemetry or upsells.
Why Login Armor
- Complete and free: every module is included under the GPL.
- Lightweight: modules load only when needed and normal login checks add less than 2 ms on a typical setup.
- Private by default: data stays on your site. Optional external calls are disabled until you enable the related feature.
- Ready for real sites: multisite support, reverse-proxy controls, WP-CLI commands and production-safe defaults.
Twelve security modules
- Hide Login: replace
wp-login.phpwith a private slug and return a 404 or redirect blocked visitors to a chosen URL. - Brute Force Protection: escalating lockouts, subnet blocking, trusted proxy headers and coverage for login, password recovery, registration, XML-RPC and REST users.
- Hardening: fifteen controls for XML-RPC, pingbacks, file editing, version exposure, application passwords, author enumeration, reserved usernames, honeypots and new-admin alerts.
- Two-Factor Authentication: TOTP, email codes, backup codes, trusted devices, per-role enforcement, grace periods and recovery.
- Detection and Incidents: group raw events into attack patterns with severity, timelines, source IPs, targeted users and one-click actions.
- Activity Log: tamper-evident admin audit trail with filters, CSV export, retention controls and optional signed SIEM forwarding.
- Security Headers: CSP, X-Frame-Options, Permissions-Policy, Referrer-Policy and X-Content-Type-Options for login and lockout pages, with optional site-wide baseline headers.
- Breach Check: privacy-preserving Have I Been Pwned password checks and an optional XposedOrNot email check.
- Password Policy: length and character rules, username exclusion, breached-password rejection and optional non-locking expiration reminders.
- Session Management: idle timeout, maximum lifetime, optional single-device access and one-click revocation of other sessions.
- IP Geolocation: cached country lookup for IPs shown in Incidents and Events, with private ranges excluded.
- Request Firewall: optional, monitor-first filtering of malicious paths, query strings and HTTP methods, with administrator exclusions and IP/path allowlists.
Additional tools
Login Armor also includes guided onboarding, a 0-100 security score, conflict detection, email/Slack/Discord/webhook notifications, a dashboard widget and a complete WP-CLI suite.
The optional AI Security Briefing uses your own WordPress AI connector to explain a thirty-day security snapshot or a single incident. It always starts with deterministic facts, works without AI and sends nothing until an administrator explicitly requests an analysis.
GPL forever. PHP 8.1+. WordPress 6.8+. Zero dependencies.
Douze modules de sécurité. Une seule extension légère. Aucune version premium.
Login Armor protège la connexion, les comptes et l’administration de WordPress grâce à douze modules indépendants. L’extension s’adresse aux agences, freelances et propriétaires de sites qui veulent une sécurité concrète, des preuves lisibles et des réglages sûrs, sans tableau de bord distant, télémétrie imposée ni upsell.
Pourquoi Login Armor
- Complet et gratuit : tous les modules sont inclus sous licence GPL.
- Léger : les modules se chargent uniquement lorsque nécessaire et les contrôles ajoutent moins de 2 ms sur une connexion normale.
- Privé par défaut : les données restent sur votre site. Les appels externes optionnels sont désactivés tant que vous n’activez pas la fonction concernée.
- Prêt pour la production : multisite, reverse proxies, commandes WP-CLI et réglages par défaut sécurisés.
Douze modules de sécurité
- Masquer la connexion : remplace
wp-login.phppar un slug privé et renvoie une 404 ou redirige les visiteurs bloqués vers l’URL choisie. - Protection contre la force brute : verrouillages progressifs, blocage de sous-réseaux, proxies de confiance et protection de la connexion, récupération, inscription, XML-RPC et REST users.
- Renforcement : quinze contrôles pour XML-RPC, les pingbacks, l’éditeur de fichiers, la version, les mots de passe applicatifs, l’énumération d’auteurs, les identifiants réservés, le pot de miel et les alertes nouvel administrateur.
- Authentification à deux facteurs : TOTP, codes par e-mail, codes de secours, appareils de confiance, application par rôle, période de grâce et récupération.
- Détection et incidents : regroupe les événements en scénarios d’attaque avec sévérité, chronologie, IP sources, comptes ciblés et actions immédiates.
- Journal d’activité : piste d’audit admin infalsifiable avec filtres, export CSV, rétention et transfert SIEM signé optionnel.
- En-têtes de sécurité : CSP, X-Frame-Options, Permissions-Policy, Referrer-Policy et X-Content-Type-Options pour les pages de connexion et de verrouillage, avec en-têtes de base optionnels sur tout le site.
- Détection de fuites : vérification confidentielle des mots de passe via Have I Been Pwned et contrôle optionnel des e-mails via XposedOrNot.
- Politique de mot de passe : longueur, classes de caractères, exclusion de l’identifiant, rejet des mots de passe compromis et rappels d’expiration non bloquants.
- Gestion des sessions : délai d’inactivité, durée maximale, accès limité à un appareil et révocation des autres sessions.
- Géolocalisation IP : pays des IP affichées dans Incidents et Événements, avec cache et exclusion des plages privées.
- Pare-feu de requêtes : filtrage optionnel, d’abord en surveillance, des chemins, requêtes et méthodes HTTP malveillants, avec exclusion des administrateurs et listes d’autorisation IP/chemins.
Outils complémentaires
Login Armor inclut aussi un assistant de configuration, un score de sécurité de 0 à 100, la détection de conflits, les notifications par e-mail, Slack, Discord ou webhook, un widget de tableau de bord et une suite WP-CLI complète.
Le briefing de sécurité IA optionnel utilise votre propre connecteur IA WordPress pour expliquer les trente derniers jours ou un incident précis. Il commence toujours par des faits déterministes, fonctionne sans IA et n’envoie rien tant qu’un administrateur ne demande pas explicitement une analyse.
Conçu par
Login Armor est conçu et maintenu par Fabrice Ducarme de WPFormation. Nous l’utilisons sur chaque site que nous livrons.
- Présentation et fonctionnement de Login Armor
- Guides de sécurité WordPress sur WPFormation
- Veille des vulnérabilités WordPress sur WPFormation
GPL pour toujours. PHP 8.1+. WordPress 6.8+. Zéro dépendance.
External Services
Login Armor has no telemetry and requires no Login Armor account. The following services are contacted only when WordPress itself or an administrator enables the related feature.
WordPress AI connector (optional)
The AI Security Briefing sends a security prompt through the administrator’s own WordPress AI connector only after they click an analysis button. Minimised mode sends counts, categories, severities and role buckets without clear IP addresses or usernames. Explicit deep mode also sends IP addresses and event details. Login Armor stores no provider API key. The selected AI provider’s terms and privacy policy apply.
Slack, Discord or custom webhook (optional)
When an administrator enables an incident notification channel, Login Armor sends the incident type, severity, IP address, target username, event count and site URL to the configured endpoint. The separate signed Activity Log forwarding option sends the event, object, user ID/login/role, IP address, description, integrity hashes, site URL and plugin version to the administrator’s SIEM or custom webhook.
- Slack: Terms | Privacy
- Discord: Terms | Privacy
- Custom webhook: terms and privacy are controlled by the administrator’s chosen endpoint.
Gravatar
The Activity Log uses WordPress core’s get_avatar(). If avatars are enabled in WordPress, a hashed email address may be sent to Gravatar to retrieve the image.
Have I Been Pwned (optional)
Breach Check and the optional compromised-password policy send only the first 5 characters of a password’s SHA-1 hash to the Pwned Passwords API. The password and full hash never leave the site. Checks fail soft if the service is unavailable.
- Have I Been Pwned: Privacy | Acceptable Use
XposedOrNot (optional)
The separate Email check, disabled by default, sends the user’s email address and a plugin-identifying User-Agent to XposedOrNot when a user is created or changes email.
ipwho.is (optional)
IP Geolocation sends a displayed public IP address to ipwho.is when an administrator opens Incidents or Events. Results are cached for 30 days. Private and reserved ranges are never sent, and developers can replace the lookup through the login_armor_geoip_lookup filter.
- ipwho.is: Service | Documentation
Screenshots
Installation
- Upload the
login-armordirectory to/wp-content/plugins/ - Activate the plugin through the ‘Plugins’ menu in WordPress
- Go to LoginArmor in the admin menu to configure
For multisite: Network Activate the plugin to apply it across all sites.
Setting up Hide Login
- Go to LoginArmor > Settings > Hide Login section
- Enter your desired login slug (e.g.,
my-login) - Save settings
- Bookmark your new login URL: you will need it to access your admin
Recovering access
If you forget your custom login URL:
- Use the recovery email feature (configurable in settings)
- Connect to your database and delete the
login_armor_hide_slugrow from thewp_optionstable - Use WP-CLI:
wp option delete login_armor_hide_slug
FAQ
-
Will it lock me out of my own site?
-
No. Hide Login always sends a one-time recovery URL to the admin email. If you lose the slug, check your inbox. The plugin also honors
wp-clifallback so you can reset anything from SSH. -
Does it slow my site down?
-
No. Everything is lazy-loaded and indexed. On a normal login flow the extra SQL cost is under 2 ms.
-
Is it compatible with Cloudflare / reverse proxies?
-
Yes. IP detection honors trusted
X-Forwarded-Forheaders; you pick the header in Settings. -
Does it work with multisite?
-
Yes, subdomain and subfolder. Each site has its own modules, logs, and thresholds.
-
Can I use LoginArmor alongside Wordfence / iThemes Security / Solid Security?
-
Yes, but disable overlapping modules on one side to avoid double lockouts.
-
Where is the data stored?
-
Three custom tables in your own database: events, incidents, activity. Nothing leaves your server.
-
How do I migrate my configuration?
-
Settings are plain WordPress options. Export/import via WP-CLI or any standard options-sync tool.
-
Is there a pro version?
-
Not currently. LoginArmor is fully free and open source. GPL forever.
-
Where can I report bugs or request features?
-
Support forum: wordpress.org/support/plugin/login-armor/.
Reviews
Contributors & Developers
“Login Armor” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Login Armor” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
2.4.6
Hide Login correction from a user report. The custom blocked-access redirect now works for both /wp-admin/ and /wp-login.php. FSE 404 templates reached through /wp-admin/ now load the public block styles required by navigation and other core blocks. Legacy redirect values remain compatible.
2.4.5
Accuracy release from a user report. Login Armor’s own blocks no longer count as failed passwords: a two-factor lockout, a two-factor rate limit, the mandatory-2FA gate, a honeypot catch and a reserved-username rejection each used to insert a brute-force attempt on top of their own sanction, so one mistyped 2FA code could push a legitimate user into the IP lockout while signing in with the correct password. Failed logins now record the real reason instead of always reporting “Wrong password”: the Events tab, the incident timeline, the Overview live tail and the CSV export distinguish a wrong password from an unknown account, cookies blocked by the browser, each of the plugin’s own gates, and a refusal coming from another plugin (shown with its code). Existing log rows keep the previous label. Also fixes a separate bug found while testing this release: the incidents table failed to create on MariaDB 11.7+/MySQL 9 because the vector column collided with a new reserved word, which silently disabled the whole Detection engine on those servers.
2.4.4
Hardening release from an external code audit; five confirmed issues fixed and each verified end-to-end (real HTTP flow locally, re-run under PHP 8.4, and validated on a live WordPress 7.0 / PHP 8.3 install). The Overview dashboard now computes the threat level and active-incident count over every active incident, so an older critical incident can no longer drop the headline back to “Normal”. A successful two-factor login now fires the canonical wp_login cycle, so failed-attempt counters reset, the login is logged, the single-session policy applies and third-party integrations run. Lockout escalation is now atomic under concurrency, so a burst of simultaneous failures can no longer turn a first offence into an immediate long ban. The Slack/Discord/generic notification webhooks are re-validated against private, reserved, link-local and IPv6-internal addresses before every send (SSRF), and CSV log exports neutralise spreadsheet formula injection from attacker-controlled fields. Plugin Check 0 ERROR.
2.4.3
Security release. Mandatory two-factor authentication is now a hard gate: a user in an enforced role who never enrolled and whose grace period has expired is blocked at login instead of being let in with only a redirect to their profile (reported by the WordPress Plugin Review Team). Existing users are never locked out unexpectedly – the grace window is started automatically the first time enforcement applies, and an admin can reopen it from the Users list (“Restart 2FA grace”) or via WP-CLI. Hardened: TOTP codes can no longer be replayed within their validity window (single-use per time-step, RFC 6238); the Activity Log webhook URL is validated against private, reserved, link-local and IPv6-internal addresses (SSRF), matching the notification channels; attacker-submitted usernames are neutralised before entering the optional AI incident prompt. A filter (login_armor_2fa_hard_enforcement) restores the previous soft behaviour if needed.
2.4.2
Coherence and lifecycle release. Fixes: deactivation now clears every scheduled task (three were left running); uninstall removes all options, user meta and caches from the newer modules (AI, Password Policy, Sessions, GeoIP, Firewall); disabling Two-Factor now asks for confirmation like every other module; the plugin’s own conflict warnings, silently hidden since 2.4.0, show again. Improvements: a composite database index speeds up brute-force lookups, open incidents are capped so the table cannot grow forever, and the admin UI is more consistent (numeric fields, empty states, module counters). New: a warning when a front-end login plugin such as Ultimate Member is active, since Two-Factor and Hide Login are not compatible with a front-end login form. No behaviour change on standard installs.
2.4.1
Fix: a “critical error” could occur during password recovery when another active plugin re-fires a WordPress core hook with an off-contract argument type or arity (for example a null passed to retrieve_password_message ahead of Login Armor). Strict parameter hints are relaxed, each with an internal type guard, on every core-hook callback across all modules; behaviour is unchanged on canonical WordPress calls. Generalises the 2.1.15 URL-builder fix to the whole plugin.
2.4.0
Feature release – request firewall, guided onboarding, fuller in-app docs.
- New – Request Firewall (optional, off by default): a PHP “8G”-style filter that blocks malicious query strings, paths and HTTP methods before WordPress fully loads (Apache/Nginx/LiteSpeed/IIS). Starts in monitor mode; admins, REST, cron, WP-CLI and admin-ajax are never filtered; IP/path allowlist (CIDR); blocks aggregate to one incident per IP per hour.
- New – Onboarding wizard with a one-click safe baseline (Simple) or manual setup (Advanced), plus a permanent “Apply safe baseline” button. Upgrading sites see no change.
- Improvement – Granular security-plugin conflict warnings, a cache-plugin warning when Hide Login is on, and contextual help for the modules added since 2.2.0.
2.3.0
Feature release – account-security hardening.
- New – Password Policy: minimum length and character-class rules, forbid the username in the password, optionally reject breached passwords (privacy-preserving HIBP), optional non-locking expiration.
- New – Session Management: idle timeout, maximum session lifetime, optional single active device, and “sign out all other devices”.
- New – IP Geolocation (opt-in): country next to IPs on Incidents/Events; lazy, cached, private ranges never sent (see External Services).
- Improvement – Score now accounts for Password Policy and Session Management; baseline headers can apply site-wide; every IP lockout creates an incident. New hardening: disable pingbacks, alert on new admin.
2.2.0
Feature release – the AI Security Briefing.
- New – AI Security Briefing on the Overview: one click turns your last 30 days of activity into a plain-language verdict, an IP picture and prioritised actions. Built on the WordPress 7 native AI Client – uses your own connector, stores no API key, runs only on click. Always leads with a deterministic facts snapshot (with or without AI); plus “Explain with AI” on an incident.
- Privacy – Minimised mode (anonymised signals) is the default; deep mode (real IPs) is an explicit opt-in. See External Services.
2.1.26
Fix: email/backup 2FA bouncing to “session expired” on browsers that don’t return the verification cookie; the form now also carries the session token. Security unchanged.
2.1.25
Fix: email/backup two-factor verification rejected in some browsers (notably Chrome); the form is now uncached and authenticated by the signed same-site cookie.
2.1.24
Fix: fatal error during authenticator-app setup on hosts whose wp-config.php does not define AUTH_KEY (e.g. some Infomaniak installs). Existing setups unaffected.
2.1.23
Fix: 2FA login screen – “use a different method” links now work, expired/locked sessions explain themselves, and the setup button reports errors.
2.1.22
Fix: the Security Score now counts default-on modules (Brute Force, Detection). Display and scoring only.
2.1.21
Cleaner user-agent labels in the Events table.
2.1.20
Migration-aware Activity Log integrity (amber “Keys changed” instead of a false TAMPERED alarm), an XML-RPC blind-spot warning, and a complete French translation.
2.1.19
Clearer attack-type labels on incidents, translatable admin toasts, French translation of the visible tabs, and an integrity-badge verify fix.
2.1.18
Fix: bulk actions now work when incidents are all resolved; the attack-vector pill shows only for XML-RPC/REST.
2.1.17
Incidents now record and show the attack vector (XML-RPC / REST / login form) and support bulk resolve/ignore.
2.1.16
Plain-permalink fixes (Hide Login URL, REST allowlist), activity-log coverage for 2FA/registration/reset, and Honeypot on WooCommerce and frontend forms.
2.1.15
Fix: fatal TypeError when plugins (e.g. WP Fastest Cache) call WordPress URL builders with off-contract argument types.
2.1.14
Fix: the prevent_author_enum toggle no longer blocks the legitimate ?author=N filter in the wp-admin Posts/Pages lists.
2.1.13
Fix: silent 2FA failure on non-trailing-slash permalinks (e.g. /%postname%) – the verify cookie path mismatched the request path.
2.1.12 and earlier
Bug fixes, security hardening and i18n across the 2.1.x and 2.0.x series (Hide Login host-awareness, CSP, lockout delivery, REST scope, IPv6, HTTP/2, Activity Log integrity), through the initial 2.0.0 release. Full per-version notes: CHANGELOG.md in the plugin folder.