To secure a WordPress site with strong passwords you do not need a longer password, you need fewer of them and a second factor. A twelve-character passphrase that nobody reuses beats a twenty-character string typed into four different sites.
The stakes are concrete: one leaked pair from an old forum is enough to open a dashboard if the owner reused it. That is why password advice for WordPress is about process, not about entropy alone.
What actually makes a password strong
Length above symbols. A phrase of four unrelated words survives guessing far longer than eight characters with a capital and an exclamation mark, and a person can type it from memory.
Uniqueness above length. A perfect password reused on a forum, a shop and a WordPress admin is one breach away from three compromises. The value of uniqueness is that a leak stays local.
Changed on suspicion, not on a calendar. Forced rotation pushes people to Summer2026! and then Summer2026!!. Rotate after a leak, after a person leaves, and after a shared password has been sent over chat.
Where passwords fail on a WordPress site
The admin account, the database password in wp-config.php, the SFTP or SSH login, the hosting panel, the mail account that receives password resets, and the application passwords used by plugins and integrations.
The mail account is the quiet one. Every reset link lands there, so an attacker who owns the mailbox owns the site without touching WordPress.
Application passwords are the second quiet one. A backup plugin with an old key keeps working after the admin password changes, and nobody remembers it exists.
The order that pays off
- A password manager for the team, one vault, one owner.
- Unique passwords for the admin, the host, the database, and the mailbox.
- Two-factor authentication on the mailbox first, then on the WordPress admin.
- A rate limit on the login form, so guessing stops being free.
- A review of users and application passwords once a quarter.
The order matters because each step closes a real path. A strong admin password with an unprotected mailbox is a locked door next to an open window.
Making the team use it
Policy documents do not change behaviour; friction does. A manager that fills the login form, an autofill that works on mobile, and a recovery path that does not require a support ticket are what make strong passwords survive the second week.
For an office, shared accounts are the main enemy. One login for three editors means one password in a chat and no way to revoke access when someone leaves. Separate accounts with roles cost nothing and make the audit possible.
What to check today
Open the users list and count administrators. More than two is usually a habit, not a need.
Open the application passwords screen and look for keys nobody recognises. Delete the ones that are not in use.
Check whether the login form has a limit and a CAPTCHA. If it does not, a strong password is the only thing between a script and the dashboard.
Check when the database password was last changed, and whether it is the same as the hosting panel password.
What passwords cannot do
A strong password does not stop a phishing page that asks for it, and does not stop a session cookie stolen from a browser. Those two cases are why the second factor exists, and why session lifetime is a security setting rather than a performance one.
It also does not protect a site whose plugin leaks data. The password is one layer, and the firewall, the update discipline and the backup are the others.
Questions we hear
Is a password manager safe?
A reputable manager with two-factor authentication is safer than human memory. The vault is one target; reused passwords are thousands of small ones.
How long should the admin password be?
Long enough to be unique and typed once. Four random words plus the manager’s generator is a practical answer, and the length matters less than the uniqueness.
Do I need to change passwords every 90 days?
No. Current guidance drops forced rotation because it produces predictable patterns. Rotate on evidence of a leak.
What about the database password?
Generate it, store it in the manager, and never reuse it in the hosting panel. A leaked wp-config.php is common in badly configured backups.
Next step
Start with the mailbox and the admin account, then add the second factor and a login limit. The two-factor authentication page covers enrollment, the brute force protection page explains the attempt counter, and the prices name the tier. NIST keeps the password guidance in its digital identity guide.
