WordPress powers a huge share of the web, which makes it the most attractive target for automated attacks. Most of those attacks are not personal. Bots scan millions of sites every day looking for weak passwords, outdated plugins and misconfigured servers, and they break into whatever they find first. A small business site is just as likely to be hit as a large one.
The good news is that most successful attacks exploit a short list of avoidable weaknesses. This WordPress security checklist covers 30 practical steps, grouped by area, from logins and updates to server hardening, backups and monitoring. It also explains which steps matter most, how often to repeat them, what to do if a site is already compromised, and where plugin-based security stops being enough.
Why WordPress Sites Get Attacked
Attackers target WordPress because of its popularity, not because the core software is weak. The WordPress core team fixes security issues quickly. The real risk comes from the ecosystem around it: tens of thousands of plugins and themes of varying quality, sites that are rarely updated, and logins protected by reused passwords.
Most attacks are automated. A bot finds a site, checks which plugins it runs, compares them with lists of known vulnerabilities and tries the matching exploit. If that fails, it tries common passwords on the login page. Nobody needs to know your business exists for this to happen. Our article on why WordPress sites get hacked explains these attack patterns in more detail.
What Attackers Want
A hacked site is valuable even if it has no customer data. Attackers use compromised sites to send spam, host phishing pages, inject links to other sites, redirect visitors to scams or mine resources from the server. Some simply use the site as a stepping stone to attack others.
For the site owner, the result is the same: lost rankings, browser warnings, blocked emails, a damaged reputation and the cost of cleanup. Prevention is far cheaper than recovery, which is why this checklist focuses on closing the most common doors first.
Why “We’re Too Small to Be a Target” Is a Myth
Automated attacks do not choose targets based on size or traffic. A local plumber’s site and a national retailer’s site look the same to a bot scanning for an outdated plugin. Small sites are often easier targets, because they are updated less often and nobody watches the logs.
Agencies managing dozens of client sites face the same risk multiplied. One forgotten site with an old plugin can become the entry point that damages a client relationship.
How to Use This Checklist
The 30 steps below are grouped into eight areas. Not every step carries the same weight, so each area starts with the steps that prevent the most common attacks. If you only have an hour, complete the critical items first and schedule the rest.
| Priority | What It Covers | When to Do It |
|---|---|---|
| Critical | Strong passwords, two-factor authentication, updates, backups | Today |
| High | User roles, removing unused plugins, firewall, HTTPS, monitoring | This week |
| Medium | Hardening settings, file permissions, upload rules, activity logs | This month |
| Ongoing | Updates, scans, backup tests, user reviews | Every week or month |
Before changing server settings or configuration files, take a full backup and, ideally, test changes on a staging copy. Some hardening steps can block legitimate functionality if they are applied without checking how the site works.
Accounts and Logins
Stolen or guessed passwords are one of the most common ways into a WordPress site. Brute-force attacks try thousands of username and password combinations, and credential stuffing reuses passwords leaked from other services. Securing logins closes this door for good.
These six steps cost almost nothing and take very little time, which makes them the best place to start.
1. Use Strong, Unique Passwords for Every Account
Every account with access to the site, including WordPress users, hosting, the database, SFTP and the domain registrar, needs a unique password. Reused passwords are dangerous because a leak on any other service exposes your site too.
Use a password manager to generate and store long random passwords. This also makes it easier to share access safely within a team and to revoke it when someone leaves.
2. Turn On Two-Factor Authentication
Two-factor authentication (2FA) requires a second step, usually a code from an app, in addition to the password. Even if a password is stolen, the attacker cannot log in without the second factor. For administrator and editor accounts, 2FA should be mandatory.
Use an authenticator app rather than SMS where possible. Store backup codes safely, so an administrator who loses a phone does not get locked out of the site.
3. Limit Login Attempts
By default, WordPress allows unlimited login attempts. Limiting login attempts and temporarily blocking addresses that fail repeatedly makes brute-force attacks impractical. Many security plugins and server firewalls offer this feature.
Blocking at the server level is better than blocking inside WordPress, because each failed attempt that reaches WordPress still uses server resources. On busy attack days, that difference matters.
4. Give Every User Only the Access They Need
Not everyone who works on a site needs to be an administrator. WordPress has built-in user roles: Editors manage content, Authors publish their own posts, and Contributors write drafts. Follow the principle of least privilege and give each person the lowest role that lets them do their job.
Review the user list regularly. Remove former employees, old agencies and freelancers who finished their project. Every unused account is a login that someone could compromise.
5. Avoid Obvious Usernames
Bots always try “admin”, the site name and the names shown on author pages first. Using an unpredictable username for administrator accounts removes half of what a brute-force attack needs to guess.
You cannot rename a WordPress user directly in the dashboard. Create a new administrator with a better username, log in with it, and delete the old account, assigning its content to the new user.
6. Control XML-RPC and Application Passwords
XML-RPC is an older interface that lets external apps talk to WordPress. It is also a popular tool for brute-force attacks, because it can test many passwords in a single request. If the site does not use the WordPress mobile app, Jetpack or another service that needs it, disable XML-RPC.
Review application passwords in user profiles too. They are useful for integrations, but each one is another way into the site, so remove any that are no longer used.
Updates and Software
Outdated software is the most common entry point for attacks on WordPress. When a vulnerability in a plugin is published, bots start scanning for sites that run the vulnerable version within days, sometimes hours. Keeping software updated closes those holes before they can be used.
Updates are also where many site owners hesitate, because an update can occasionally break something. The answer is a safe update process, not avoiding updates.
7. Keep WordPress Core, Plugins and Themes Updated
Install security updates as soon as possible, and keep up with regular updates too. WordPress applies minor core updates automatically by default, but plugins and themes need attention. Check for updates at least weekly, and act on security releases immediately.
For important sites, update on a staging copy first or take a backup right before updating. This way, if an update causes a problem, you can roll back in minutes. Our article on what WordPress maintenance includes covers a safe update routine.
8. Delete Unused Plugins and Themes
Deactivated plugins and themes can still be exploited, because their files remain on the server. If you are not using a plugin or theme, delete it, do not just deactivate it. Keep one default WordPress theme as a fallback and remove the rest.
Also check for abandoned plugins: ones that have not been updated in a long time or were removed from the official directory. Replace them with maintained alternatives before a vulnerability is found.
9. Only Install Software from Trusted Sources
Download plugins and themes only from the official WordPress directory or directly from reputable developers. Nulled plugins and themes, which are pirated copies of premium products, very often contain hidden backdoors and malware. The money saved is never worth the risk.
Before installing a new plugin, check when it was last updated, how many active installations it has, and whether the developer responds to support questions. A plugin is code that runs on your server with full access to your site.
10. Run a Supported PHP Version
WordPress runs on PHP, and old PHP versions stop receiving security fixes after a few years. Running an unsupported version leaves the server exposed to known vulnerabilities, no matter how well WordPress itself is configured.
Check the PHP version in your hosting panel or in WordPress under Tools, Site Health. Upgrade on a staging copy first, because some older plugins may not work with newer versions.
Hosting and Server Security
Your hosting provider controls the environment WordPress runs in. A secure server isolates sites from each other, keeps software patched and filters malicious traffic before it reaches the site. Weak hosting can undermine every other step on this list.
These steps are partly in your hands and partly in your host’s. If your current host cannot help with them, that is a strong sign it is time to move.
11. Choose Hosting with Proper Isolation and Security
On cheap shared hosting, one compromised site can sometimes affect others on the same server. Good managed WordPress hosting isolates each site, keeps the server software updated, monitors for malware and provides automatic backups. Ask your host specifically how sites are isolated and what happens when an attack is detected.
For agencies hosting many client sites, isolation is critical. A breach on one client’s site should never give access to another client’s files or database.
12. Use HTTPS Everywhere
An SSL certificate encrypts traffic between visitors and the site, protecting login details and form submissions from interception. Free certificates are available from most hosts, so there is no reason to run a site without HTTPS.
After installing the certificate, make sure every page redirects from HTTP to HTTPS and that the WordPress and site URLs in the settings use https. Mixed content, where some files still load over HTTP, weakens the protection and triggers browser warnings.
13. Put a Firewall in Front of the Site
A web application firewall (WAF) filters malicious requests, such as exploit attempts, vulnerability scans and login floods, before they cause harm. Firewalls can run inside WordPress as a plugin, at the server level, or at a CDN like Cloudflare.
Where the firewall runs makes a big difference, which we explain in the comparison section below. In short, the earlier a bad request is stopped, the less it costs the server.
14. Set Correct File Permissions
File permissions control who can read, write and execute files on the server. Permissions that are too open let attackers modify files or upload malicious code. As a general rule, directories should not be writable by everyone, and wp-config.php should be readable only by the owner and the web server.
Your host can usually set the recommended permissions for you. The official WordPress hardening guide lists the standard values and explains why they matter.
15. Secure Database Access
The database holds all of the site’s content, users and settings. Use a unique database user with a strong password for each site, and never share one database user between several sites. Make sure the database is not reachable directly from the internet unless there is a specific need.
Changing the default table prefix from wp_ adds only a small obstacle and is not a substitute for real security, but it does no harm on new installations.
WordPress Hardening
Hardening means changing default settings that are convenient but risky. None of these steps is dramatic on its own, but together they make it much harder for an attacker to turn a small foothold into full control of the site.
Most of these changes are made in wp-config.php or in the server configuration. Back up the file before editing it, because a single typo can take the site offline.
16. Disable File Editing in the Dashboard
WordPress lets administrators edit theme and plugin files directly from the dashboard. If an attacker gets into an admin account, that editor becomes an easy way to insert malicious code. Adding DISALLOW_FILE_EDIT to wp-config.php removes the editor completely.
Developers should edit files through version control or SFTP anyway, so this rarely affects legitimate work.
17. Protect wp-config.php
The wp-config.php file contains the database credentials and the security keys for the site. Block direct web access to it in the server configuration, and make sure it has strict file permissions. On some servers it can also be moved one directory above the web root.
Never leave copies of this file, such as wp-config.php.bak or wp-config.old, on the server. Backup copies with a different extension can sometimes be downloaded as plain text.
18. Block PHP Execution in the Uploads Folder
The uploads folder must be writable, because WordPress stores media there. That also makes it a favourite place for attackers to drop malicious PHP files. Blocking PHP execution in wp-content/uploads ensures that even if such a file is uploaded, it cannot run.
This is a simple server rule that most hosts can add in minutes, and it stops a whole category of attacks.
19. Refresh Security Keys and Salts
WordPress uses security keys and salts in wp-config.php to protect login cookies. If you suspect a breach, or if the keys were never set properly, generate new ones. Changing them logs out every user immediately, which is exactly what you want after a security incident.
WordPress.org provides a free generator for new keys. Replace the existing lines in wp-config.php and log in again.
20. Disable Directory Listing
If directory listing is enabled, visitors can browse the contents of folders that have no index file, such as plugin directories. This reveals which plugins and versions are installed, which helps attackers choose an exploit. Disabling directory browsing in the server configuration closes this information leak.
Check it by opening a URL like yoursite.com/wp-content/uploads/ in a browser. You should see an error or a blank page, not a list of files.
21. Limit Information about Your Setup
Version numbers in the page source, readme files and detailed error messages tell attackers exactly what software you run. Hiding them is not real protection on its own, but there is no reason to advertise details. Turn off error display on the live site and log errors to a file instead.
The most important part of this step is still updating. Hiding a version number does not make an outdated plugin safe.
Backups and Recovery
Even with every precaution, something can still go wrong: a zero-day vulnerability, a compromised hosting account or a human mistake. Backups are what turn a disaster into an inconvenience. A clean, recent backup is often the fastest way to recover from a hack.
Our full guide on how to back up a WordPress site covers methods and tools in detail. The three steps below are the minimum for a secure setup.
22. Back Up Daily and Store Copies Offsite
Back up both the files and the database, at least daily for active sites, and keep copies offsite, not only on the same server. If the server is compromised or fails, backups stored on it may be lost or infected too.
Follow the 3-2-1 approach where possible: three copies of your data, on two different types of storage, with one copy offsite.
23. Keep Several Versions
Malware often sits quietly on a site for days or weeks before anyone notices. If you keep only the latest backup, it may already be infected. Keep multiple versions going back several weeks, so you can restore a copy from before the infection.
Label or note backups taken before major changes, such as a redesign or a large plugin update, so they are easy to find later.
24. Test Your Restores
A backup that cannot be restored is not a backup. Test a restore on a staging site every few months to confirm the files are complete and the process works. It is much better to discover a problem during a calm test than during an emergency.
Write down the restore steps, including where backups are stored and who has access. In a crisis, a clear procedure saves hours.
Monitoring and Detection
Security is not a one-time setup. New vulnerabilities appear every week, and some attacks are designed to stay hidden. Monitoring tells you when something changes, so you can react before visitors, clients or Google notice.
These four steps give you early warning of most problems.
25. Scan for Malware Regularly
A malware scanner checks files and the database for known malicious code, suspicious changes and injected links. Scan at least daily on important sites. Look for a scanner that checks all file types, including archives such as zip files, because attackers sometimes hide malicious code where simple scanners do not look.
When a scan finds something, act quickly. Our guide to WordPress malware removal explains how to clean a site properly.
26. Monitor Uptime
Downtime can be a sign of an attack, a resource problem caused by malicious traffic, or a broken update. Uptime monitoring checks the site every few minutes and alerts you when it stops responding. Without it, you may find out from a client or customer hours later.
Combine uptime alerts with your other monitoring. If a site goes down at the same time as a spike in blocked requests or a new file appears on the server, you know to treat it as a security incident, not just a hosting hiccup.
27. Keep an Activity Log
An activity log records who logged in, which settings changed, which plugins were installed and which content was edited. After an incident, it shows what happened and when. Day to day, it helps you spot suspicious logins or changes made by an account that should not be active.
Review the log after any unexpected change and periodically for administrator activity.
28. Watch Google Search Console Security Reports
Google notifies site owners in Search Console when it detects hacked content, malware or harmful downloads on a site. If Google finds a problem, it may show warnings to visitors or remove pages from search results. Make sure every site has Search Console set up and that notifications reach someone who reads them.
Google’s help page on security issues explains the different types of reports and how to request a review after cleaning a site.
Forms, Uploads and Third-Party Code
Every place where visitors can send data to the site is a potential entry point. Contact forms, file uploads, comments and registration forms all need protection. The same is true for code you load from other services.
These final two steps cover the parts of a site that are easy to forget during a security review.
29. Restrict File Uploads and Protect Forms
If forms accept file uploads, restrict them to the file types you actually need, limit file size, and store uploads outside public folders where possible. Archives deserve special attention, because a zip file can contain malicious code that a basic check misses. Add spam protection, such as a CAPTCHA or honeypot, to all public forms.
Disable registration if the site does not need user accounts. Open registration with a default role higher than Subscriber is a common misconfiguration that gives attackers an account on your site.
30. Review Third-Party Scripts and Integrations
Tracking codes, chat widgets, embedded tools and API integrations all run code or exchange data with other services. If one of those services is compromised, your site can be affected. Keep a list of every third-party integration, remove the ones no longer used, and limit API keys to the permissions they need.
Store API keys and passwords outside the database and theme files where possible, and rotate them when someone with access leaves the team.
Plugin Firewalls vs. Server-Level Protection
Security plugins are a good start, and many sites rely on them as their main protection. It is worth understanding their limit, though. A plugin firewall runs inside WordPress, so by the time it decides to block a request, the server has already started PHP, loaded WordPress and opened a database connection. For a single request, that cost is tiny. During an attack with thousands of requests per minute, it can overload a small server.
| Feature | Security Plugin Firewall | Server-Level Protection |
|---|---|---|
| Where it runs | Inside WordPress, after PHP loads | In front of WordPress, before PHP loads |
| Server cost per blocked request | PHP worker, WordPress boot, database connection | Very low, the request never reaches WordPress |
| Behaviour during traffic spikes | Can slow down or crash a small server | Keeps resources free for real visitors |
| Protection if WordPress is broken | Limited, the plugin may not load | Still active |
| Setup | Easy, installed as a plugin | Needs server or hosting-level configuration |
The best setup combines both: protection at the server or network level that stops obvious attacks early, and WordPress-level tools for things like two-factor authentication, activity logs and user management. The goal is to stop as much bad traffic as possible before it reaches WordPress.
What to Do If Your WordPress Site Is Hacked
If you see signs of a hack, such as unknown admin users, spam pages in Google, redirects to strange sites or a browser warning, act calmly and in order. Rushing into changes can destroy the evidence you need to find the entry point.
Follow these steps:
- Contain the problem. Put the site in maintenance mode if visitors are being redirected or exposed to malware.
- Change all passwords. Update WordPress, hosting, database and SFTP passwords, and refresh the security keys in wp-config.php.
- Find the entry point. Check the activity log, server logs and recently modified files to understand how the attacker got in.
- Clean or restore. Remove malicious code and unknown users, or restore a clean backup from before the infection, then update everything.
- Close the hole. Update or remove the vulnerable plugin or theme, and apply the hardening steps from this checklist.
- Request a review. If Google flagged the site, request a review in Search Console once the site is clean.
Restoring a backup without finding the entry point usually leads to reinfection within days. If you are not sure how the attacker got in, get professional help before putting the site back online.
A Simple Security Routine
Security works best as a routine rather than a reaction. The table below turns this checklist into recurring tasks, so nothing is forgotten after the initial setup.
| Frequency | Tasks |
|---|---|
| Daily | Automated backups, malware scans, uptime monitoring |
| Weekly | Plugin, theme and core updates, review security alerts |
| Monthly | Review users and roles, check the activity log, remove unused plugins, check Search Console |
| Quarterly | Test a backup restore, review hosting and PHP versions, rotate important passwords and keys |
| After any incident | Change all passwords, refresh security keys, run a full scan, find and fix the entry point |
For agencies, this routine is also a clear service to offer clients. It is easy to explain, easy to report on and it protects both the client’s site and your relationship with them.
Common WordPress Security Myths
A few beliefs keep many sites less secure than they should be. Clearing them up helps you focus your time where it actually reduces risk.
The first myth is that one security plugin is enough. A plugin is useful, but it cannot fix weak passwords, outdated software, poor hosting or missing backups. Security is a combination of layers, and each layer covers gaps in the others.
The second is that hiding the login page solves brute-force attacks. Changing the login URL reduces noise, but it does not replace strong passwords, two-factor authentication and rate limiting. Treat it as a minor extra, not a defence.
The third is that a site is safe once it has been cleaned. Without closing the original entry point and monitoring afterwards, cleaned sites are often reinfected quickly. Recovery is only complete when the cause is fixed.
How Webueno Handles WordPress Security
At Webueno, security is built into how we host and maintain WordPress sites, not added as an afterthought. Our managed approach covers the full checklist: regular updates handled through the platform, daily offsite backups, uptime monitoring, malware scanning and cleanup when something goes wrong.
For protection against attacks, we built The Gatekeeper, a server-level security layer for WordPress. It works as a small gate in front of WordPress that refuses bad requests before PHP, plugins or the database ever load, so visitors still get the page and editors still get in. On one production WordPress site, it stopped around seventeen thousand attacks in 23 days, with about a third of all requests turned away before they reached PHP.
The Gatekeeper also includes a scanner that checks every kind of file, including the contents of zip archives, and Sentinel, which explains unusual cases in plain language, so your team can tell a client what happened without reading server logs.
For agencies, everything is available white-label. Security cleanups, hardening and ongoing maintenance are handled as tickets in the Webueno platform, with tracked time and clear reports you can pass on to clients under your own brand.
Make Security Part of Every Site You Manage
Most WordPress hacks are preventable. Strong logins, regular updates, good hosting, sensible hardening, reliable backups and steady monitoring close the doors that automated attacks look for. Work through this checklist once, then turn it into a routine.
If you manage client sites and want this handled properly without adding to your team’s workload, Webueno can take care of it for you. Create a free Webueno account and send us your first security ticket today.
Frequently Asked Questions
These are the questions we hear most often from site owners and agencies about keeping WordPress secure.
Is WordPress Secure Enough for Business Websites?
Yes. The WordPress core is actively maintained and security issues are fixed quickly. Most hacked sites are compromised through outdated plugins, weak passwords or poor hosting rather than WordPress itself. With good maintenance and the steps in this checklist, WordPress is a secure platform for business sites.
What Is the Most Important WordPress Security Step?
If you can only do a few things, keep everything updated, use strong unique passwords with two-factor authentication, and keep daily offsite backups. Together, these prevent most attacks and make recovery fast if something still goes wrong.
Do I Need a Security Plugin?
A security plugin is useful for features like two-factor authentication, login limits and activity logs. It should not be your only protection. Server-level filtering, good hosting, updates and backups cover the risks a plugin cannot handle on its own.
How Do I Know If My WordPress Site Has Been Hacked?
Common signs include unknown admin users, unfamiliar pages or links in Google results, redirects to other sites, browser or Search Console warnings, sudden slowdowns and unexpected changes to files. Regular malware scans and an activity log help you catch these signs early.
How Often Should I Update WordPress Plugins?
Check for updates at least once a week and install security updates as soon as they are released. Take a backup before updating, or test updates on a staging copy for important sites, so you can roll back quickly if something breaks.
Can a Hacked WordPress Site Be Fully Recovered?
In most cases, yes. A site can be cleaned or restored from a clean backup, and Google warnings can be removed after a review. Full recovery also means finding and closing the entry point, changing all passwords and monitoring the site afterwards to prevent reinfection.