Black FridayCyber Monday 2026
14Days
15Hrs
22Mins
43Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress Login Security: Strong Passwords, Two-Step Login and Limits

Most break-ins start at the login screen. Use this practical checklist for passwords, two-step login, admin accounts, attempt limits and HTTPS.

wpallsolution Updated 6 min read

WordPress login security is about making the page where people log in hard to attack and hard to misuse. Automated bots try common passwords on login pages all day, and a single weak or reused password on an administrator account can undo every other safeguard. The good news is that the main protections are simple and mostly free: strong unique passwords, two-step login, fewer administrator accounts, limits on attempts and HTTPS. This guide goes through them in a practical order and notes what each one does and does not do.

Quick answer

Give every user a long, unique password kept in a password manager, turn on two-step authentication for all administrators, keep the number of administrators small and give everyone else the lowest role that works, limit repeated login attempts at your host, firewall or a plugin, serve the admin over HTTPS and plan a safe recovery. The WordPress hardening guide recommends strong passwords and two-step authentication, limiting the database user’s privileges, disabling file editing in the dashboard and keeping software updated. No measure makes a site unhackable.

How this guide was prepared: it is research-based. We used the WordPress hardening documentation and the WordPress source listed under Sources, checked on October 23, 2026. Features such as two-step login or passkeys depend on your setup or on plugins, so check what yours supports. We do not claim that any measure prevents all attacks, and we are not a cybersecurity firm.

Why the login page is a target

Every WordPress site has a predictable login address, so bots can try stolen or guessed passwords at scale. The usual ways in are weak or reused passwords, accounts that nobody remembers, and too many people with administrator rights. A successful login gives an attacker the same power as the account owner, including installing plugins, so protecting accounts matters more than hiding the login URL. Our article on PHP2Shell and website security covers server-level issues, which are a separate layer.

The decision tree: how strong is your login?

Flowchart for WordPress login security: five questions about passwords, two-step login, administrator accounts, attempt limits and HTTPS
Five questions show where your login is weakest.
  1. Every admin has a long, unique password? If not, fix that (Step 1).
  2. Two-step login enabled for admins? If not, turn it on (Step 2).
  3. Many Administrator accounts? Reduce them (Step 3).
  4. Unlimited password attempts? Add limits (Step 4).
  5. Admin on HTTPS, recovery planned? Check both (Step 5).

5 steps to improve WordPress login security

Step 1: Use strong, unique passwords

The WordPress hardening guide advises strong passwords: mixed characters, no names or words tied to you or your site, no short or single-type passwords, and the strength meter when you change one. A password manager makes unique long passwords practical. Never reuse a password from another service, and change any that may have been exposed. Avoid the username “admin”, as the guide also notes.

Step 2: Turn on two-step login

Two-step authentication asks for a second proof, such as a code from an app or a device-based passkey, in addition to the password, so a stolen password alone is not enough. The hardening guide recommends enabling it. WordPress core does not necessarily include it on every version, so use a trusted plugin or your host’s feature, and check the plugin’s update history. Passkeys follow the W3C Web Authentication standard and replace the password with a device credential; support depends on your plugin. Keep recovery codes safe, and test the login in a private window.

Step 3: Keep administrators few and use least access

Give each person the lowest role that lets them work: editors do not need administrator rights, and former staff or agencies should have their accounts removed or downgraded when the job ends. WordPress stores roles and capabilities in the database, and an account with the wrong role is a risk; see “You are not allowed to access this page” for how roles work. Review the Users list regularly for accounts you do not recognise. Also review Application Passwords, a core feature since WordPress 5.6 that lets an account give a script or app access, and revoke the ones you do not use.

Step 4: Limit repeated attempts

Bots try many passwords quickly, so limit how often one source can attempt a login. Your host, a firewall or a security plugin can lock a source out after several failures or add a delay. Set limits that do not lock out real staff, and log what is blocked. Also keep WordPress, plugins and themes updated, because outdated software is another way in; see how to update WordPress plugins safely.

Step 5: Use HTTPS and plan a safe recovery

The hardening guide recommends requiring an encrypted HTTPS connection for administration, so passwords are not sent in the clear, and using SFTP instead of plain FTP. Make sure the admin and login pages load over HTTPS without warnings; see WordPress mixed content warnings. Plan recovery: where recovery codes are kept, who can reset access, and how you would regain control if an account were compromised. If a login problem blocks you, see WordPress login redirect loop.

Version and hosting differences

  • Managed hosts may already offer two-step login, login limits or a firewall; ask what is included.
  • Changing the login URL can reduce bot noise but is not a replacement for the steps above.
  • Multisite has separate super admin accounts that need the same care.

How to verify your login security

  • Every administrator uses a unique password and a second step.
  • The Users list contains only people who should be there.
  • Repeated wrong passwords are blocked or slowed.
  • You tested login and recovery in a private window.

Common mistakes

  • Sharing one administrator account between several people.
  • Leaving old agency or freelancer accounts active.
  • Installing several security plugins that overlap.
  • Locking yourself out with limits and no recovery plan.

Frequently asked questions

Is two-step login necessary?

It is one of the most effective extra steps for administrator accounts, and the WordPress hardening guide recommends it.

Should I hide the login page?

It can reduce noise, but strong credentials and limits matter more.

Can a security plugin do everything?

No. It helps with attempts and monitoring, but passwords, roles and updates are still your responsibility.

What if I lose my second factor?

Keep recovery codes and know who can reset access before you need it.

Related guide: WordPress Redirecting to Spam Sites: First Steps for a Redirect Hack

Related guide: Stop WordPress Form Spam: Honeypot vs Turnstile vs reCAPTCHA

What to do next

Work through the five steps for every administrator account. wpallsolution offers WordPress maintenance packages that include login hardening in higher tiers, shown on the pricing page. We are not a cybersecurity firm and cannot promise that a site will never be attacked.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us