Checklists
WordPress Security Hardening Checklist
A practical checklist for hardening a business WordPress website: updates, user access, MFA, server settings, firewalls, backups and ongoing monitoring.
- Published
- Updated
- Reading time
- 5 min read
WordPress powers a large share of business websites, which is exactly why automated attacks target it constantly. Most successful compromises do not involve anything sophisticated: they exploit an outdated plugin, a reused password or an administrator account that should have been removed years ago. Hardening is the process of closing those easy routes in, one by one.
Use this checklist to review a WordPress site you are responsible for. Work through it in order, because the early sections remove the most common risks. Some items need hosting or server access; where you do not have it, note the item and raise it with your host or maintenance provider. No checklist can make a site unhackable, but every item you complete makes an attack less likely to succeed and easier to detect.
Before you start
Hardening changes can lock people out or break features if they are applied carelessly. Prepare first.
- Take a full backup of files and database. Store it off the server, so you have a clean starting point if anything goes wrong.
- Use a staging copy where possible. Test server-level changes, such as file permission or PHP changes, on staging before applying them to the live site.
- List everyone who needs access. Note each person, their role and the level of access they genuinely need.
- Record what you change. A simple change log makes it easy to reverse a step and to explain later what was done.
Updates and software inventory
Outdated software is one of the most common entry points. Once a vulnerability (CVE) in a popular plugin is publicly disclosed, automated tools start scanning for sites that have not yet applied the fix.
- Update WordPress core to the current release, and confirm minor security releases are applied automatically.
- Update every plugin and theme, testing key journeys such as forms and checkout afterwards. Our WordPress security service follows a staging-first process for exactly this reason.
- Remove inactive plugins and themes. Deactivated code can still be exploited if its files remain on the server. Keep one default theme as a fallback.
- Replace abandoned plugins. If a plugin has not been updated by its developer for a long time, or has been closed in the WordPress.org directory, find a maintained alternative.
- Check premium licences. Lapsed licences often mean no more updates, which quietly turns a paid plugin into a security risk.
- Run a supported PHP version. PHP versions that have reached end of life no longer receive security fixes from the PHP project.
If keeping up with updates is the hard part, a structured security patch management routine is the most effective single improvement you can make.
Users, passwords and authentication
Stolen, reused and guessed credentials are another common way in.
- Audit all user accounts. Remove former staff, agencies and freelancers. Downgrade anyone who does not need administrator rights to Editor or Author.
- Avoid obvious administrator usernames such as "admin", and make sure public author names do not reveal login usernames.
- Enforce strong, unique passwords stored in a password manager, never shared by email or chat.
- Enable multi-factor authentication for every administrator and any account that can install plugins or edit code. See our glossary entry on MFA for how it works.
- Limit login attempts with rate limiting at the firewall or plugin level, to slow down brute-force attacks.
- Review application passwords and API keys created for integrations, and revoke any that are no longer used.
WordPress configuration
A few settings in wp-config.php and the dashboard remove whole categories of risk.
- Disable file editing in the dashboard by setting DISALLOW_FILE_EDIT to true in wp-config.php, so a compromised admin account cannot edit plugin or theme code directly.
- Use unique authentication keys and salts. Regenerate them after any suspected compromise, which also signs out all users.
- Turn off debug output on the live site. Error messages displayed to visitors can reveal file paths and software versions.
- Disable XML-RPC if nothing uses it. It is a common target for password-guessing attacks. Check first, because some apps and integrations rely on it.
- Review user registration settings. If the site does not need public registration, make sure it is turned off, and check the default role is Subscriber.
Server and file system
These items usually need hosting access. If your site is on shared hosting, ask your host which are already in place.
- Set correct file permissions. Typically 644 for files and 755 for directories, with wp-config.php more restrictive where the host allows.
- Block PHP execution in the uploads directory. Uploaded files should never run as code, and this single rule stops many backdoors.
- Use SFTP or SSH, not plain FTP, and remove any FTP accounts that are no longer needed.
- Isolate sites from each other. Several sites under one hosting account can infect each other; separate them where possible.
- Enforce HTTPS across the whole site with a valid certificate and redirects from HTTP.
- Add security headers such as Strict-Transport-Security, X-Content-Type-Options and a sensible Content-Security-Policy, testing carefully before enforcing.
Firewall and bot protection
A web application firewall filters malicious requests before they reach WordPress.
- Put a WAF in front of the site, either at the DNS/CDN level or on the server. Website firewall management covers rule tuning so legitimate visitors are not blocked.
- Protect the login and admin areas with rate limiting, bot challenges or, for small teams, IP restrictions.
- Review blocked traffic periodically to spot targeted attacks and false positives.
Backups and recovery
Hardening reduces risk; backups are what you rely on when something still goes wrong.
- Run automated off-site backups of files and database, on a schedule that matches how often the site changes.
- Keep enough history. A retention period of several weeks helps if an infection is discovered late.
- Test a restore to a separate environment at least quarterly. An untested backup is an assumption, not a plan.
Monitoring and ongoing review
Hardening is not a one-off project. New vulnerabilities appear every week.
- Monitor uptime and SSL expiry so outages and certificate problems are spotted quickly.
- Enable file integrity monitoring to alert you when core or plugin files change unexpectedly.
- Scan for malware regularly, and know the signs your website has been hacked so you can act early.
- Log administrator activity such as logins, plugin installs and user changes.
- Repeat this checklist quarterly, and after any major change to the site or team.
Need a second pair of eyes?
If you would like an independent view of how your WordPress site measures up, request a free website health check and we will highlight the most important gaps to close first.