wp2shell: more than a month later. Confirm 6.8.6, 6.9.5, 7.0.2. Patched is not clean.

Read the advisory

Password Management Tips for WordPress Sites

Numbered password practices for WordPress: unique passwords, managers, team sharing, 2FA, recovery codes, and audits without duplicating the full login guide.

Topics Login & access Hardening & checklists

Lars Koudal

Lars Koudal

Updated Published

Passwords still matter. Most opportunistic WordPress attacks are recycled credentials and weak admin passwords, not clever zero-days. Treat this page as the password hub, then use the full login security guide for lockouts, rename login, and endpoint hardening.

Password Management Tips

10 password practices that reduce risk

1. Unique password for every important account

Reuse is how one breach becomes twenty. WordPress, email, hosting, DNS, and payment dashboards each get their own secret. Weak patterns we still see: top WordPress passwords.

2. Prefer long random passwords

Aim for 16+ random characters from a generator. Length and uniqueness beat clever pet-name substitutions. Summer2026! is not a strategy.

3. Use a password manager

Bitwarden, 1Password, and similar tools beat browser-saved Password123! across five client sites. The manager creates, stores, and fills secrets so you are not improvising under deadline.

4. Share access the safe way (teams and freelancers)

  • Invite people through the manager’s shared vault or one-time secret link
  • Never paste admin passwords into Slack, email, or tickets
  • Prefer individual WordPress users with the lowest role that works over one shared “team admin”
  • Revoke the vault item and the WordPress user the day a contractor finishes

5. Turn on 2FA for privileged roles

Two-factor authentication stops many stolen-password logins. Prioritize administrators and anyone who can install plugins. Authenticator apps are the practical default.

6. Store recovery codes offline

When you enable 2FA, save recovery codes in the manager’s secure notes or a printed offline copy. Losing the phone without recovery codes is how people lock themselves out and then weaken security to get back in.

7. Audit passwords and users on a schedule

Quarterly is enough for many sites; monthly for busy agencies:

  • Unexpected administrators
  • Reused or ancient passwords after staff changes
  • Application passwords and REST tokens you no longer need
  • Hosting and SFTP accounts that still belong to old vendors

8. Do not rely on the browser’s password jar alone

Browser save is better than nothing on a personal laptop. It is a poor plan on shared computers, and it rarely covers hosting panels or DNS. Use a real manager as the source of truth.

9. Treat phishing as a password problem

Fake “urgent login” emails and cloned wp-login pages steal real credentials. Do not click login links from unexpected mail. Open the site from your bookmark or manager. After a suspected phish, rotate the password and confirm 2FA still stands.

10. Rotate after people leave or anything looks wrong

Forced monthly rotation for everyone is usually worse than unique long secrets plus 2FA. Do rotate when:

  • A freelancer or employee leaves
  • A password may have leaked
  • You find an unknown admin (midnight admin pattern)
  • Hosting or email was compromised

WordPress-specific gotchas

  • Application passwords and REST API tokens are credentials too; revoke what you do not need
  • “Remember me” on shared computers is a gift to the next user
  • Password-protected posts only hide content; they are not a locked-down admin
  • Host and FTP/SFTP credentials get the same treatment as wp-admin

Where Security Ninja fits

Passwords are the human layer. Pro login protection adds failed-login limits and optional login URL changes. 2FA stops many stolen-password logins even when the password leaks.

Pair with Cloud Firewall so noisy bots never reach the form as often.

After a suspected leak

  1. Change the compromised password everywhere it was reused
  2. Review users for unknown admins
  3. Enable or re-check 2FA and recovery codes
  4. Scan for malware if the account had install privileges (malware removal)

Bottom line

Unique passwords, a manager, careful sharing, 2FA, and recovery codes beat most botnet noise. Shrink admin access and let login protection handle the brute-force layer. Pricing for Pro, Free on WordPress.org.

Found this useful? Share it.

Larger screenshot