Most WordPress sites are compromised in ordinary ways: an out-of-date plugin, a reused password, a leaked key. This checklist is ordered by impact, so you can stop when you run out of time and still have fixed the biggest risks. Tick each item off, and revisit the list whenever you add a plugin or a user.
Updates and software
- Keep WordPress core updated. Leave automatic minor and security updates on.
- Update plugins and themes promptly. Most breaches come through outdated plugins, not core.
- Delete what you do not use. Inactive plugins and themes still contain code that can be exploited.
- Remove abandoned plugins. If a plugin has not been updated in a long time or is closed, replace it.
- Use a supported PHP version. Old versions stop receiving security fixes.
- Watch for vulnerability reports for the plugins you use, through a monitoring service or plugin.

Accounts and logins
- Use strong, unique passwords and a password manager.
- Turn on two-factor authentication for every account that can publish or administer.
- Limit the number of administrators. Give people the lowest role that lets them do their job.
- Do not use “admin” as a username and remove accounts that are no longer needed.
- Limit login attempts and rate-limit the login page.
- Review users regularly, especially after staff or contractors leave.
Backups and recovery
- Back up automatically, at least daily for active sites.
- Store backups off the server, so an attacker cannot delete them with the site.
- Test a restore at least once. An untested backup is a hope, not a plan.
- Write a one-page recovery plan: who to call, where backups live, how to restore.
Hosting and server
- Use HTTPS everywhere and redirect HTTP to HTTPS.
- Choose a host that isolates accounts and patches its servers.
- Use SFTP or SSH, never plain FTP.
- Set safe file permissions: 755 for directories, 644 for files, and stricter permissions for
wp-config.php. - Disable file editing in the dashboard by adding
define( 'DISALLOW_FILE_EDIT', true );towp-config.php. - Use unique security keys and salts in
wp-config.php.
Protection and monitoring
- Run a firewall. A plugin firewall or a cloud firewall in front of the site blocks common attacks.
- Scan for malware on a schedule.
- Keep an activity log of logins, content edits and plugin changes.
- Disable XML-RPC if you do not use it, or restrict it.
- Add security headers such as
X-Content-Type-Optionsand a sensible Content Security Policy where practical. - Monitor uptime and get alerts when the site changes unexpectedly.
Good habits
- Test updates on staging for important sites.
- Audit every few months: users, plugins, backups and the items above.
If you only do five things
- Update everything and delete unused plugins.
- Turn on two-factor authentication.
- Set up off-server backups and test a restore.
- Use a firewall.
- Keep an activity log.
Final thoughts
Security is a routine, not a one-time project. A short monthly review that checks updates, users and backups prevents most of the incidents that make the news.
Frequently asked questions
Is WordPress secure?
WordPress core is well maintained. Most compromises come from plugins, themes, weak passwords and neglected updates, which you control.
Do I need a security plugin?
A good one adds a firewall, scanning and login protection, but it does not replace updates, backups and strong accounts.



