This WP security checklist is built for agencies responsible for many client sites, not for a single blogger. It focuses on the controls that prevent most real incidents (accounts, updates, plugins, backups, and monitoring) and ends with the part most checklists skip: what to do in the first hour after something goes wrong.
The WP Security Checklist
Last reviewed: November 2026. Version-specific advice in this checklist, such as supported PHP versions, plugin names and WordPress settings, changes over time. Confirm it against current official documentation before you apply it to a client site.
How to use this WP security checklist
Run it when you onboard a site, then review it quarterly. Each item is either a setting you can confirm or a process you can prove. If you cannot show evidence for an item, treat it as not done.
Short answer: Secure WordPress by keeping core, themes, and plugins updated through staging, removing unused and abandoned plugins, using unique admin accounts with two-factor authentication, applying hardening settings, running a firewall and malware scanning, keeping offsite backups with tested restores, and monitoring uptime and file changes.
1. Accounts and Access
- Every person has their own account. No shared “admin” logins.
- Two-factor authentication is required for administrators and editors.
- Administrator role is limited to people who need it. Editors stay editors.
- Former staff, freelancers, and old agencies are removed.
- Application passwords and API keys are listed and rotated when people leave.
- Login attempts are rate limited.
2. Updates and Plugins
- Core, themes, and plugins are updated at least weekly, tested on staging first.
- Plugins with no updates in the last 12 months are reviewed for replacement.
- Nulled or pirated themes and plugins are never used.
- Inactive plugins and themes are deleted, not just deactivated.
- Vulnerability alerts are monitored for every installed plugin.
- PHP is on a supported version. WordPress.org recommends PHP 8.3 or greater.
3. Hardening Settings
The official WordPress hardening guide is the reference. These are the settings we confirm on every site:
| Setting | Why |
|---|---|
| Disable file editing in the dashboard (DISALLOW_FILE_EDIT) | Stops attackers editing code through a stolen admin login |
| Correct file permissions | Limits what a compromised process can change |
| Unique security keys and salts | Invalidates stolen cookies when rotated |
| HTTPS everywhere with HSTS | Protects logins and form data in transit |
| XML-RPC disabled if unused | Removes a common brute force target |
| Security headers | Reduces clickjacking and content injection risk |
4. Protection and Monitoring
- A web application firewall at the host, CDN, or plugin level.
- Daily malware scanning and file change detection.
- Uptime monitoring with a person who responds, not just an alert inbox.
- Admin activity logging for logins, plugin changes, and user changes.
- Forms protected from spam without inaccessible CAPTCHAs.
The OWASP Top 10 is a useful reference when reviewing custom code and API integrations.
5. Backups
- Daily backups stored offsite, separate from the hosting account.
- At least 30 days of retention.
- A snapshot before every update batch.
- A test restore at least quarterly, documented.
6. Incident Response Plan
When a site is compromised, the first hour matters. Write this down before you need it.
- Contain: put the site in maintenance mode or block traffic if it is serving malware.
- Preserve: take a copy of the compromised files and logs before cleaning.
- Reset: rotate all passwords, salts, API keys, and hosting credentials.
- Clean or restore: restore from a known clean backup, then update everything.
- Find the cause: identify the vulnerable plugin or account and fix it.
- Communicate: agree who tells the client and what they are told. Payment or personal data may trigger legal notification duties, so involve the client’s counsel.
- Review: request removal of any search engine or browser warnings and monitor closely.
What a care plan covers in this checklist
Agencies often ask which of these steps a maintenance plan handles and which are separate projects. The split below is typical. Exact inclusions differ by plan tier, so check the website care page for what each Softvole tier covers, and read what WordPress maintenance plans should include for the wider picture.
| Checklist area | Usually inside a care plan | Usually quoted separately |
|---|---|---|
| Accounts and access | Periodic review of admin users on request | Custom roles, single sign-on or a full access audit |
| Updates and plugins | Core, plugin and theme updates with checks afterwards | Replacing abandoned plugins or rebuilding the features they provided |
| Hardening settings | Checks on standard WordPress security settings | Server, firewall or hosting changes outside WordPress |
| Protection and monitoring | Uptime and basic security monitoring | Penetration testing and formal compliance audits |
| Backups | Scheduled backups and restore checks | Moving to a new backup or hosting setup |
| Incident response | First response and triage of an alert | Large cleanup or rebuild work after a breach, scoped per incident |
Running Security Across Many Sites
Agencies rarely fail on knowledge. They fail on consistency across 20 or 50 sites. A WordPress audit at onboarding plus a standard maintenance plan fixes that. Softvole runs this checklist on every site in our white label care plans, with branded reports for your clients.
Agency triage: severity, owner and cadence
When one agency looks after many sites, every finding needs a severity, a named owner and a time to act. Use the table as a starting model and set your own response times in each client agreement.
| Severity | Example | Owner | Act within (example) | Recurring check |
|---|---|---|---|---|
| Critical | Site hacked or defaced, malware found, checkout or payment page compromised | Agency account lead with the care partner | Same day, start the incident plan | Daily monitoring alerts |
| High | Plugin with a public exploit, backups failing, admin account compromised | Care partner, agency informed | 1 to 2 business days | Weekly update and vulnerability review |
| Medium | Outdated plugins with no known exploit, admins without two-factor authentication | Care partner | Next maintenance window | Monthly maintenance run |
| Low | Unused themes, old user accounts, minor hardening gaps | Agency and client together | Next quarterly review | Quarterly security review |
Security Review Schedule
| Frequency | Tasks |
|---|---|
| Daily | Backups, malware scan, uptime checks |
| Weekly | Updates through staging, vulnerability alerts review |
| Monthly | User account review, activity log review, form tests |
| Quarterly | Restore test, plugin necessity review, credentials rotation for shared tools |
| Yearly | Full audit and hardening review |
How to Talk About Security With Clients
Clients do not buy firewalls. They buy confidence that the site will not embarrass them or leak customer data. Frame security in plain outcomes: the site stays online, customer information stays private, and if something goes wrong you can restore it within hours. Then show the evidence monthly in a short report.
The Threats This Checklist Defends Against
Understanding the most common attacks helps prioritize the checklist instead of treating every item as equal.
| Threat | How it works | Checklist controls that stop it |
|---|---|---|
| Vulnerable plugin exploit | Automated bots scan for known flaws in outdated plugins | Updates, vulnerability alerts, removal of abandoned plugins, firewall |
| Credential stuffing and brute force | Bots try leaked or common passwords on wp-login | Unique accounts, strong passwords, two-factor authentication, rate limiting |
| Malicious admin from a former contractor | Old accounts are reused or sold | Account reviews, removing former staff and agencies |
| Nulled theme or plugin backdoor | Pirated code contains hidden access | Licensed code only, file integrity monitoring |
| Spam and form abuse | Bots submit forms at scale | Spam protection, rate limiting, server firewall |
| Server-level compromise | Weak hosting isolation or outdated server software | Reputable hosting, supported PHP, offsite backups |
Least Privilege in Practice
Most sites have more administrators than they need. A practical rule: only people who install plugins or change settings need the Administrator role. Content writers should be Authors or Editors; a shop manager role suits WooCommerce staff. Review roles every month as part of care, and remove accounts the same day someone leaves a team, including staff at previous agencies.
Shared logins are particularly risky. When several people use one “admin” account, you cannot see who did what, you cannot remove one person without changing the password for everyone, and two-factor authentication becomes impractical.
Passwords and Two-Factor Authentication
Require a password manager for anyone with administrator access. Long, unique passwords stop credential stuffing because a password leaked elsewhere will not work here. Two-factor authentication with an authenticator app adds a second barrier even if a password is stolen. For clients who resist two-factor authentication, start with administrators only and expand later.
How to Vet a Plugin Before Installing It
- Updated within the last few months and tested with the current WordPress version.
- Active installs and reviews that suggest real use and support.
- A developer or company with a security contact and a track record of fixing issues quickly.
- Does one job well rather than bundling dozens of unrelated features.
- Can be removed cleanly if needed.
- Not available only from an unofficial source.
Every plugin is code running on the client’s server. Fewer, better-maintained plugins reduce the attack surface and the update workload.
Extra Controls for WooCommerce and Membership Sites
Stores and membership sites hold customer accounts, order history, and sometimes payment tokens. Use a reputable payment gateway so card data never touches the server. Restrict access to order and customer data with appropriate roles. Monitor for unusual account creation and failed logins. Keep checkout pages excluded from page caching and test them after every update. Our guide to WordPress client portals covers additional controls for sites with private user areas.
How to Prove Security Work to Clients
Security is invisible when it works, which makes it hard to value. Provide evidence each month: the number of updates applied, vulnerabilities patched, blocked login attempts, backup status with the date of the last tested restore, and any incidents with their resolution. Over a year, that record shows clients what they would be exposed to without care, and it supports renewal conversations.
Common Security Mistakes Agencies Make
- Keeping one shared admin login for the whole agency team.
- Installing a security plugin and assuming the job is done.
- Leaving staging sites public and unprotected, often with weaker passwords.
- Storing backups only on the same server as the site.
- Never testing a restore until a real emergency.
- Forgetting to remove access for freelancers after projects end.
A Backup Strategy That Survives Real Incidents
The widely used 3-2-1 approach works well for WordPress: keep at least three copies of the data, on two different types of storage, with one copy off-site. For most client sites that means the live site, a daily backup with the host or backup service, and a separate copy in independent cloud storage that the hosting account cannot delete. Add a pre-update snapshot before every batch of updates. Ransomware and compromised hosting accounts can delete backups stored alongside the site, which is why the independent copy matters.
Securing Staging and Development Sites
Staging sites are often forgotten and therefore attractive to attackers. They may run old plugins, use weak passwords, or contain copies of customer data. Protect staging with password protection at the server level, block search engines, keep plugins updated just like production, and avoid copying real customer data unless necessary. Remove old staging sites once projects end.
Compliance Considerations
Some sites carry obligations beyond general security. Stores that take card payments must follow payment industry standards, which is easiest when a hosted payment gateway keeps card data off the server entirely. Sites that collect personal data may be subject to privacy laws depending on location and audience, which affects consent, retention, and breach notification. Sites for healthcare or financial clients may have additional rules. Agencies should not give legal advice, but they should flag these questions early and ask the client to confirm requirements with their counsel.
Security Steps When You Take Over a Site
- Take an offsite backup before changing anything.
- List all administrator accounts and confirm each with the client.
- Reset passwords and security salts, and enable two-factor authentication.
- Update or replace vulnerable and abandoned plugins.
- Scan for malware and compare core files against official versions.
- Set up monitoring and a regular update schedule.
These six steps close most of the risk inherited from previous vendors within the first week.
Warning Signs Worth Investigating Immediately
- New administrator accounts nobody recognizes.
- Unexpected redirects to other sites, especially on mobile or from search results.
- Unfamiliar files in uploads or core folders.
- Sudden spikes in outgoing email or form submissions.
- Search results showing spam titles for the client’s domain.
- Browser or search engine warnings about the site.
Any of these deserves an immediate response following the incident plan above. Waiting a day often turns a contained problem into a public one.