DD DevDome Track. Protect. Grow.
Security

The WordPress Security Checklist: 15 Things That Actually Matter

Most lists have fifty items and three that matter. This one has fifteen, ranked by how many real incidents each one would have prevented.

On this page
  1. Prevent: the three that stop most attacks
  2. Reduce: remove what you do not need
  3. Detect: know when something is wrong
  4. Recover: assume one day it fails
  5. How the items rank, and why
  6. What to skip
  7. The rhythm

A WordPress security checklist is only useful if it is short enough to finish. This one has fifteen items, ordered by how many real compromises each would have prevented, grouped into prevent, reduce, detect and recover. The first three items alone stop most attacks. The last section tells you what to skip.

Prevent: the three that stop most attacks

1. Update everything, promptly. Core, plugins, themes, PHP. Nearly every mass compromise uses a vulnerability that was already patched. Turn on automatic updates for plugins with a clean track record; do the rest weekly, one at a time, with a check between.

2. Unique, long passwords on every account. From a password manager, never reused from another site. Credential stuffing, trying leaked email and password pairs, succeeds only when passwords are reused.

3. Two-factor authentication for administrators and editors. A guessed or leaked password is then not enough. Small dedicated plugins add app codes or passkeys in minutes.

Reduce: remove what you do not need

4. Delete inactive plugins and themes. Inactive code is still on disk, still reachable and still a hiding place. Keep one default theme as a fallback and delete the rest.

5. Prune accounts and roles. Remove ex-staff accounts, downgrade anyone who does not need publish or admin rights, and make sure no account is called admin.

6. Disable XML-RPC unless something uses it. It allows hundreds of password guesses per request. The mobile app and a few services need it; most sites do not.

7. Close open registration. If Anyone can register is ticked and you do not run a membership or shop that needs it, untick it. If you do need it, the default role must be Subscriber.

8. Set file permissions and disable file editing. Standard permissions on folders and files, and the constant that turns off the theme and plugin editors in the admin, so a compromised admin account cannot write PHP from the dashboard.

9. Use an edge firewall if you have one. Cloudflare or your host’s web application firewall filters known attack patterns before they reach your server. If you have it, turn it on; if you do not, a PHP-level firewall is the fallback.

Detect: know when something is wrong

10. Scan files against WordPress.org. A scanner that verifies core, plugin and theme files against their official checksums, looks for backdoor patterns in the rest, and checks the database for injected content. DevDome Malware Scanner does this with the evidence shown per finding, quarantine instead of deletion, and one-click repair of official packages, with no account needed for scanning. Schedule it weekly. We make it, so weigh that; the verification approach is what to look for.

11. Handle bots and brute force without CAPTCHAs. Limit login attempts, and run bot detection that recognises scanners by behaviour. DevDome Bot Protection records what it would block before you turn blocking on, which is the safe way to tune any blocker.

12. Keep an activity log. Logins and failed logins with IPs, user and role changes, plugin and settings changes. DevDome Activity Log records these locally with filters, search and CSV export, all free. It is the difference between “we were hacked” and “this account logged in from this IP on Tuesday and installed this plugin”.

13. Monitor uptime and certificate expiry. A hacked redirect, a white screen and an expired certificate all look the same to a visitor: gone. An outside check that tests content, plus a certificate expiry alert, tells you first.

Recover: assume one day it fails

14. Backups you have actually restored. Off-site, automatic, with a retention of at least a few weeks, and tested by restoring to a staging site at least once. A backup that has never been restored is a hope.

15. A written recovery plan. Where the backups are, how to roll back a plugin, who to contact at the host, how to end all sessions and rotate keys. Half a page, kept somewhere not on the site.

How the items rank, and why

The order is not arbitrary. Published breach analyses of WordPress sites point at the same causes year after year: a vulnerable plugin or theme that had a patch available, a weak or reused password, and occasionally a compromised host or neighbouring site. Items one to three address the first two directly and together would have prevented the large majority of incidents in those reports. The reduce group shrinks the number of doors; every inactive plugin and every spare admin account is one more place for a patched-later vulnerability to live. The detect group accepts that something will eventually get through and makes sure you learn about it in days rather than months, which is the difference between a cleanup and a rebuild. The recover group is for the day the rest fails. Nothing in the list is exotic, and that is the point: the sites that get hit are rarely the ones with the most sophisticated attackers, just the ones with the most ordinary gaps.

What to skip

Three items appear on every long list and change very little:

  • Hiding the WordPress version. Scanners do not read the version; they try the exploit regardless.
  • Renaming the login URL. Hides the door from the laziest bots only. Harmless, not protection.
  • CAPTCHAs on every form. Solved by services for cents, paid for by your real visitors in abandoned forms.

Spend the time on items one to three instead.

The rhythm

First pass: an afternoon. Weekly: updates. Monthly: read the scan summary and glance at the activity log. Quarterly, or after any staff change: the whole list again. A site maintained on that rhythm is not unhackable, nothing is, but it is no longer the easiest target on the block, and that is what the bots are looking for.

Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.

Key takeaways

  • Updates, unique passwords and two-factor prevent the large majority of real WordPress compromises. Do those three before anything else.
  • Remove what you do not use: inactive plugins and themes, unused admin accounts, XML-RPC, open registration.
  • Detect, do not just defend: a file scanner that verifies against WordPress.org, an activity log and bot protection that records before it blocks.
  • Backups you have tested restoring are the item that turns a bad day into a short one.
  • Skip the theatre: hiding the WordPress version, renaming the login URL and CAPTCHAs change little.

Sources

  1. WordPress.org: Hardening WordPress : the official hardening guidance this list is built on
  2. WordPress.org: Two-factor authentication : adding 2FA to accounts
  3. WordPress.org: Brute force attacks : login protection recommendations

Links last checked October 17, 2026.

Frequently asked questions

What is the single most important WordPress security step?

Keeping core, plugins and themes updated. Nearly every mass compromise exploits a vulnerability that already had a patch available. Second is unique strong passwords with two-factor for every account that can publish or administer.

Do I need a security plugin?

You need the functions: file verification, bot and brute-force handling, logging. Whether that is one suite or two small plugins is a preference. What you do not need is a plugin whose main feature is hiding the WordPress version.

Is a firewall necessary?

Something should filter obviously bad requests. If your host or Cloudflare provides an edge firewall, that covers it with no load on your server. A PHP-level firewall plugin is a fallback when you have no edge option.

How often should I go through this list?

The first pass is an afternoon. After that, updates are weekly, the scan and log review are monthly, and the full list once a quarter or after any staff change.

DevDome Team WordPress plugin builders

The DevDome team builds lightweight, performance-first WordPress plugins and free tools for site owners, founders and marketers. We write about the exact problems our plugins solve, in plain language for people who run real sites.