---
title: Two-step login on WordPress: what actually stops account takeover
description: A stolen password should not be enough to run your site. What the research says about two-step login, which methods hold up, and how to roll it out without a revolt.
url: https://ironhelmsuite.com/blog/two-step-login-stops-account-takeover/
---

# Two-step login on WordPress: what actually stops account takeover

A stolen password should not be enough to run your site. What the research says about two-step login, which methods hold up, and how to roll it out without a revolt.

Published 2026-05-19 in Security.

Most WordPress break-ins we see do not start with a clever exploit. They start with a password that someone already has: reused from another site that leaked, guessed from a list, or typed into a fake login page. Once an attacker is in as an administrator, they do not need a vulnerability. They install a plugin.

Two-step login is the cheapest fix for that whole category of problem, and the numbers behind it are unusually clear.

## What the research says

In 2019 Microsoft wrote that multi-factor authentication blocks more than 99.9 percent of the account compromise attacks it sees across its cloud services, which process hundreds of millions of fraudulent sign-in attempts a day.

Google published a more detailed study the same year with researchers from New York University and the University of California, San Diego. A code sent by text message blocked all of the automated bot attacks they measured, 96 percent of bulk phishing and 76 percent of targeted attacks. A prompt on a phone the account was already signed into did better: 99 percent of bulk phishing and 90 percent of targeted attacks. Physical security keys stopped every attack in the study.

Two things stand out. Even the weakest second step removes almost all automated attacks, which is what most small sites face. And the method matters once someone is targeting you specifically.

## Which second step to use

**An authenticator app** (Google Authenticator, Microsoft Authenticator, 1Password, Bitwarden and many others) is the sensible default. It generates a six-digit code that changes every 30 seconds, using the time-based one-time password standard, RFC 6238. Nothing travels over the phone network, and it works offline.

**Email codes** are easy for clients who will never install an app. They are only as safe as the inbox, so they suit editors more than administrators.

**Text messages** are the weakest option. NIST's digital identity guidelines (SP 800-63B, revised in July 2025) treat codes sent through the phone network as a restricted method, because numbers can be redirected through SIM swaps and carrier tricks. Better than nothing, not what we would choose.

**Passkeys and security keys** are the strongest. They are bound to your site's domain, so a lookalike phishing page cannot use them. We cover them in a separate article.

## Rolling it out without a revolt

The technical part takes minutes. The human part is where rollouts fail.

- **Start with administrators.** They can install code. Editors and authors can wait a week.
- **Give a setup window.** Asking people to set it up at their next login, with a few days of grace, beats locking them out on a Monday morning.
- **Trust the device, within reason.** Asking for a code on every single login trains people to hate it. Remembering a device for two to four weeks is a reasonable trade.
- **Plan recovery before you need it.** Backup codes, a second administrator, or command-line access for the person who owns the server. A lost phone should be a nuisance, not an emergency.

## What it does not fix

Two-step login protects the login. It does not patch a vulnerable plugin, and it does not stop someone who already has a logged-in session cookie. Keep updates current and keep the number of administrator accounts small: every admin is a door.

In Ironhelm, two-factor login supports authenticator apps and email codes, can be required by role with a setup window, and can remember a person's own device for a period you choose. Passkeys count as a second factor on their own.

## Sources

- Microsoft Security Blog, [One simple action you can take to prevent 99.9 percent of attacks on your accounts](https://www.microsoft.com/en-us/security/blog/2019/08/20/one-simple-action-you-can-take-to-prevent-99-9-percent-of-account-attacks/) (August 2019)
- Google Security Blog, [New research: How effective is basic account hygiene at preventing hijacking](https://security.googleblog.com/2019/05/new-research-how-effective-is-basic.html) (May 2019)
- NIST, [SP 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management](https://csrc.nist.gov/pubs/sp/800/63/b/4/final) (July 2025)
- IETF, [RFC 6238: TOTP, Time-Based One-Time Password Algorithm](https://datatracker.ietf.org/doc/html/rfc6238)
