How to Protect Your WordPress Site From Stolen Logins
An unexpected password reset email deserves a closer look. An unfamiliar administrator account calls for prompt investigation. Both can signal that someone is trying to gain access to your WordPress site or has already done so.
If you run your site without a security team, start with a manageable routine: protect the accounts with the most access, learn which changes to investigate, and decide who to contact if something goes wrong. You don’t need to handle every technical task yourself.
How Accounts Fall Into the Wrong Hands
An account takeover (ATO) happens when someone uses a legitimate account without permission. An attacker might sign in with stolen credentials or use a stolen session to act as someone already logged in. Protecting an account therefore includes its password, authentication methods, active sessions, and recovery options.
Stolen Passwords
Credential stuffing means taking username and password pairs exposed in a breach and trying them on other websites. It differs from guessing a password: the attacker already has a pair that worked elsewhere. If your WordPress administrator password also unlocked an account that leaked, an attacker can try those credentials on your site.
For example, a contributor might reuse the same password across several services. If one service is breached, someone could try the exposed credentials on your login page. That sign-in may succeed without a long series of failed attempts.
Convincing Messages
A fake email claiming your site needs attention can lead to a lookalike login page. That page may capture a password and the one-time code from an authenticator app. NIST’s guidance states that one-time code authentication is not phishing-resistant.
When a message asks you to sign in or verify access, open the service through a route you already trust rather than following the message’s link.
Access That Stays Open
Attackers can also use stolen session tokens or cookies to access legitimate accounts. These can let an attacker act within an account without repeating the usual sign-in process. That’s why recovery needs to address active sessions as well as passwords.
Build a Safer WordPress Sign-In Routine

Work through these actions, starting with administrator accounts. They have the broadest access to change your site.
Use a Unique Password and Protect the Recovery Email
Let a password manager generate a password you haven’t used anywhere else, and make sure every administrator does the same. The email address attached to your WordPress account can receive password reset messages, so protect it with its own unique password and a second login step. IC3 recommends unique passwords and multifactor authentication wherever supported.
Add a Second Step for Administrators
Two-factor authentication (2FA) requires another form of verification beyond your password. One option is an authenticator app, which generates temporary codes you enter during sign-in. An attacker who has only your password would still need the second factor.
WordPress core does not include 2FA. Its official guidance directs administrators to a suitable plugin or identity provider, a service that manages sign-ins. Several WordPress security plugins can add this second step to your login screen. After setup, save your recovery codes somewhere secure. The Two Factor plugin supports signing in with previously enabled backup codes when your usual authentication method is unavailable.
Test that you can sign in successfully and find your recovery codes before relying on the new setup. Remember that a fake login page can collect an authenticator code along with a password, so keep checking where you’re signing in.
Consider Passkeys Where Supported
WordPress’s brute-force guidance suggests passkeys (WebAuthn) through a reputable plugin as a phishing-resistant login option. Passkeys use the real site’s address during authentication to resist lookalike login pages. If a maintained plugin or your sign-in provider supports them, evaluate them for administrator accounts and check the recovery process before switching.
Ask Your Host About Login Throttling
Throttling slows or pauses repeated failed login attempts. Ask your host or security plugin provider how its limits work and how you can recover access if you’re blocked.
There is no single correct number of failed attempts to allow. Restrictions also need to fit your collaborators’ access needs: a country block, for example, could lock out someone who travels. Test the settings against the way you and your team sign in before relying on them.
Give Collaborators Only the Access They Need
Publishing work doesn’t automatically require an Administrator account. The default Editor role can publish and manage posts, including posts written by other users. Review what each collaborator needs to do before assigning a role. Fewer administrator accounts means fewer accounts with permission to install plugins or add users.
Keep software maintenance on the list too. WordPress’s hardening guidance recommends keeping plugins updated. Updates address software risks, while passwords, authentication, and permissions protect account access. An updated site can still be exposed through a reused administrator password.
Spot Suspicious Activity and Take Back Control
Prevention reduces risk, but you still need a way to notice account misuse and respond. Decide who will review unusual activity and who can help if you lose access.
Check Related Changes
Watch for account changes you didn’t make, verification requests you didn’t trigger, and new users you didn’t add. A single failed login or a sign-in from a new city can have an innocent explanation. Review it alongside other activity rather than treating every alert as proof of a takeover.
An unexpected password reset followed by a new administrator account and a changed email address warrants urgent investigation. Record the sequence and timing so your host or administrator can understand what happened.
Know When Extra Detection Helps
Start with unique passwords, 2FA, throttling, and appropriate user roles. If your site holds customer accounts or repeated abuse gets past those controls, consider whether an additional login-risk service would help. These services assess whether sign-ins look suspicious. Some can request extra verification before allowing access, often called step-up verification.
CHEQ describes its offering for ATO prevention as a layer that works alongside existing authentication systems. Based on custom risk thresholds, it can block confirmed threats or trigger step-up verification through the authentication system you already use.
The service deploys through a lightweight tag or server-side API. Confirm with your developer or host how that fits your WordPress setup, along with support and pricing, before choosing a service.
Respond in Order
If you believe an account has been misused, work through these steps with your hosting or administrator. You don’t need to edit configuration files yourself.
- Record what you noticed and when. WordPress’s incident guidance recommends documentation as the first actionable step. Save the symptoms and timing for whoever investigates.
- Contact your host through a channel you already trust, such as its support portal, rather than a link in the suspicious message.
- From a device you trust, reset the exposed password. Confirm that your account’s email address hasn’t changed and secure the recovery email account too.
- Ask your host or administrator to end active sessions. WordPress’s incident guidance describes updating the site’s authentication secret keys to clear active logins. Have someone comfortable with configuration files handle this safely.
- Have the unauthorized access investigated and the site cleaned up, then change credentials again once that work is done.
Ask the investigator to check for unknown administrator accounts, unauthorized plugins, and remaining access. Don’t assume that a password reset or backup restore has addressed every part of the compromise.
FAQs
Does WordPress include two-factor authentication?
No. WordPress core doesn’t include it. The official guidance points administrators to a suitable plugin or identity provider. Start with administrator accounts, and save recovery codes during setup.
Are authenticator codes completely phishing-proof?
No. NIST states that one-time code authentication is not phishing-resistant. A fake login page can collect a code along with your password. Keep 2FA enabled because it adds protection against someone using a stolen password alone. Consider supported passkeys if you want a phishing-resistant sign-in method.
Do I need a dedicated login-risk service?
That depends on your accounts, the abuse you’re seeing, and the support needed to run it. Before choosing any service, confirm how it connects to WordPress, which activity it evaluates, and who will manage its responses.
What if I lose my phone?
If you use the Two Factor plugin and previously enabled backup codes, you can use one to sign in when your usual method is unavailable. Keep those codes in a secure place you can access without your phone. If you have no backup method, contact another site administrator or your host for help restoring access.
WordPress Plugins
Start selling products, sending newsletters, publishing ads, and more through your own WordPress website using our premium WordPress plugins.



Good guide to protecting WordPress logins.