· 7 min read · Mert Tati
How to Secure a WordPress Site: A 12-Step Checklist (2026)
A 12-point WordPress security checklist: updates, passwords, 2FA, hidden login, login limits, XML-RPC, spam, rate limiting, backups, WAF and SSL.
Short answer: securing a WordPress site isn’t a single setting, it’s a layered setup. Keep core, themes and plugins up to date; use strong passwords and two-factor authentication for admins; narrow down the login entry points (wp-login.php, XML-RPC, username leaks) and limit login attempts. Underneath all that, add regular backups, good hosting, a web application firewall (WAF) and SSL.

Why should WordPress security be layered?
Because WordPress is one of the most common content management systems on the internet, bots know it by heart: the login URL, the XML-RPC file and the REST endpoint that lists users are the same on every site. Most attacks aren’t aimed at you specifically; bots scan the internet, try the known doors and take over whichever site they find open. That’s why you need complementary layers rather than a single measure: if one is bypassed, the next one kicks in.
We’ve split the list below into three groups: account and login security, forms and traffic, and infrastructure. For each item, we also state clearly what a plugin can handle and what belongs on the hosting or server side.
WordPress security checklist: 12 items
- 1. Core, themes and plugins are up to date; unused themes and plugins have been deleted.
- 2. Every account has a strong, unique password stored in a password manager.
- 3. Two-factor authentication (2FA) is enabled on administrator and editor accounts.
- 4. The login URL has been moved to a hidden path, and wp-login.php and wp-admin are closed to the outside.
- 5. Failed login attempts are limited, and you get an alert the moment a lockout happens.
- 6. XML-RPC login and system.multicall are disabled.
- 7. Usernames don’t leak through the REST API, ?author=1 or the sitemap.
- 8. Comments, forms and user registrations pass through a bot filter.
- 9. Rate limiting is in place against request floods that overload the site.
- 10. There are automatic backups, stored off-site, with a restore that has actually been tested.
- 11. Hosting is reliable, with a firewall (WAF) and malware scanning at the server or CDN level.
- 12. The entire site runs over HTTPS, and the SSL certificate renews automatically.
Account and login security (1-7)
Updates: Most security holes come in through an outdated plugin or theme. Turn on automatic minor updates and take a backup before major ones. Plugins that are deactivated but not deleted still sit on the server as files; delete the ones you don’t use. To track which of your plugins have known vulnerabilities, you need a separate vulnerability scanning service or a tool from your hosting provider.
Passwords and 2FA: Leaked password lists are attackers’ main raw material. Use unique, long passwords for every account and enable 2FA with an authenticator app for administrators; even if a password is stolen, the second step stops the login. Don’t use admin, your site name or your email address as a username.
Login entry points: Moving wp-login.php to a hidden path cuts most automated traffic, but it isn’t the only door. xmlrpc.php is a separate login entry point, and with system.multicall many passwords can be tried in a single request. Usernames also leak through the REST API, author archives, the sitemap and differing login error messages. We cover these steps in detail in our guide to changing the WordPress login URL.
Login limits: By default, WordPress allows unlimited password attempts. Lock out an IP after a set number of failed attempts within a set time window, apply longer lockouts to repeat offenders, and get an email when a lockout happens. If your site is behind Cloudflare, make sure the IP being counted is the real visitor IP.
Forms, registrations and traffic (8-9)
Spam and fake registrations: Comments, contact forms and open user registration are bots’ second biggest target. Fake sign-ups can trigger an email for every new account and burn through your mail quota; form spam buries genuine customer inquiries. An invisible honeypot field, a time-to-submit check and a per-IP submission limit filter out most bots without reCAPTCHA. For details, see our article on stopping WordPress spam without reCAPTCHA.
Rate limiting: Search requests, 404 scans and form floods aren’t served from cache; every request runs PHP and hits the database. Giving each IP a per-minute budget and temporarily stopping anyone who exceeds it with a 429 takes pressure off the server. A large-scale flood, however, should be cut off at the CDN or hosting level before it reaches the server; a plugin can only stop requests that make it to PHP.
Infrastructure: backups, hosting, WAF and SSL (10-12)

These items aren’t the job of a login security plugin, and they shouldn’t be; they’re solved at the server and service level.
- Backups: Take automatic daily backups, store them somewhere other than the server your site runs on, and test a restore at least once. A backup you haven’t tested isn’t a backup.
- Hosting: Choose a host with an up-to-date PHP version, isolation between sites and server-level malware scanning.
- WAF: A firewall that filters attacks such as SQL injection and XSS runs on a CDN like Cloudflare or on the hosting side. Country blocking and large-scale DDoS protection also happen here.
- SSL: The whole site should load over HTTPS, HTTP requests should redirect to HTTPS, and the certificate should renew automatically. Passwords on the login form should never travel in plain text.
- File level: File permissions, file change monitoring and protecting wp-config.php on the server side are matters of hosting and server configuration.
Doing it with one plugin: what Hushfort covers and what it doesn’t
After incidents on our own sites and client projects, we at Tati Creative built the Hushfort WordPress security plugin, which brings items 3-9 of this list together in a single panel. The modules are aware of each other; they all share the same IP resolution, the same allowlist and the same activity log.
- Two-Factor Authentication: TOTP-based, with the QR code generated inside the plugin and downloadable recovery codes; admins without 2FA are flagged in the dashboard.
- Hide Login: wp-login.php and logged-out wp-admin requests get a 404 or a redirect; admin-ajax, the REST API and WP-Cron are unaffected.
- Limit Login & Alerts: Configurable threshold, window and lockout duration; longer lockouts for repeat offenders and lockout emails to multiple addresses.
- Surface Hardening: Disables XML-RPC login without breaking pingbacks, rejects multicall, closes four places that leak usernames and makes login error messages uniform. The Surface Scan measures all of this by sending real requests to your site.
- Spam Shield and Registration Protection: Comment and form protection without reCAPTCHA, registration limits per IP and per network, a circuit breaker and a Cleanup Wizard.
- Load Protection: A per-minute point budget per IP, a temporary 429 for anyone who exceeds it and blocking of fake Googlebots; WooCommerce checkout is never blocked.
To be honest, there are things Hushfort doesn’t do: malware scanning and cleanup, file integrity monitoring, an SQL injection/XSS firewall, backups, plugin vulnerability scanning and country blocking are not part of Hushfort. For those, you need your hosting provider’s tools, a WAF such as Cloudflare and a separate backup solution. Updates, password choices and SSL also remain routine work for you or your maintenance team.
If you’d rather not manage the infrastructure yourself, our Izmir-based team’s software, hosting and maintenance service covers managed servers, SSL, daily backups and monitoring, plus update and security maintenance.
Where should you start?
- Today: take a full backup, run updates, delete unused plugins and change admin passwords.
- This week: enable 2FA for admins, hide the login URL, and turn on login limits and XML-RPC blocking.
- This month: start spam and registration protection in test mode, add rate limiting, test a backup restore, and review WAF and SSL settings with your hosting provider.
Frequently asked questions
Is WordPress secure, or is it inherently vulnerable? WordPress core is mature software that receives regular security updates. Most problems come from outdated plugins, weak passwords and default entry points left open; in other words, it’s largely a matter of management.
Is a single security plugin enough? For the login, form and traffic layer, a single modular plugin can be enough; but backups, a WAF, malware scanning and SSL are the job of your infrastructure, not a plugin. Plan both together.
Do security measures slow down a site? Heavy solutions that scan files on every page load can. With a login-focused, modular approach, disabled modules do no work, and blocked bot requests actually reduce server load.
Does a small site really need all this? Yes. Bots don’t care how big your site is; small sites are often easier targets because they go unmaintained. The first seven items on the list can be done in an afternoon.
Summary: WordPress security starts with updates and strong passwords, gets stronger with 2FA, a hidden login, login limits and disabling XML-RPC, and protects your forms and server with spam filtering and rate limiting. Backups, a WAF, malware scanning and SSL are the infrastructure’s job; set up both together.