The monthly WordPress security checklist for agencies

Monthly WordPress security checklist

THE SHORT ANSWER

A WordPress security checklist should run monthly, not once. Each month, confirm core, plugins, themes and PHP are current, review admin users, 2FA and application passwords, check the firewall and failed logins, verify off-site backups and test a restore, scan files for malware, check SSL, domain and DNS records, test every form, and send the client a short report.

Most WordPress security checklists are a list of things to do once, at launch. Real sites get hacked months later, when nobody is looking: a plugin goes unpatched, an old contractor keeps an admin login, the backup job fails quietly or the domain lapses.

This is the checklist we use as a monthly review, grouped the way the work actually happens: updates, users and access, firewall, backups, files, SSL and DNS, forms and spam, and the report to the client. Every item says what to check, what good looks like, and why it matters. There is a printable version near the end.

Applies to: WordPress 6.8 to 7.1, PHP 8.3 to 8.5, Wordfence 9, Cloudflare Last verified: November 2026.

01How the monthly checklist fits with daily and weekly jobs

This checklist is built around a rhythm. Machines do the daily and weekly work. A person does the monthly review, because the monthly review is where judgment matters: is this admin account still needed, is this plugin abandoned, did the backup actually restore, does this DNS record belong here.

CadenceWho or what does itExamples
DailyAutomatedBackups for busy or ecommerce sites, uptime checks, firewall rules updating, malware signature updates
WeeklyAutomated, with alerts to a personPlugin and theme updates, scheduled malware scans, backups for quieter sites, vulnerability advisory check
MonthlyA person, with this checklistUser and access review, backup restore spot check, file integrity, SSL and domain expiry, DNS review, form test, client report
QuarterlyA person, deeperFull restore to a test site, plugin stack review, hosting and PHP version review, access audit for hosting, registrar and DNS accounts

Once you have a routine, the monthly pass is quick for one site. Across 30 client sites it adds up, which is why agencies batch it into one day, hand it to a care plan team, or both. We run a version of this check every week on our own site, and a few items below come straight from what it caught.

One rule before you start: record what you find. A checklist you tick in your head leaves no trail. Use a shared sheet or your care plan tool, one row per site per month, with a status of OK, Warning or Action for each group. That record becomes the client report at the end of this guide.

Want this handled for every client site?

Our white label care plans cover security, updates, backups and fixes, all under your agency brand.

See care plans

02Updates, versions and vulnerabilities

The WordPress Advanced Administration handbook puts it plainly: the most important step is keeping WordPress core, plugins and themes up to date. Many compromises come through a known plugin flaw that already had a patch available. Your monthly job is to confirm the update process is working, not just to click Update.

Core, plugins and themes

  • Confirm WordPress core is on the current release. Minor and security releases install automatically on most sites, but check that they did. A site stuck on an old minor version usually means auto-updates are blocked by a constant, a filter or a host setting.
  • List every plugin and theme with a pending update. Anything pending for more than a week needs a reason written down (for example, waiting on a staging test).
  • Update premium plugins and themes too. Licensed products such as Divi, Gravity Forms or a page builder add-on only update if the license key is active. An expired key is a security problem, not just a billing one.

Abandoned and closed plugins

A plugin with no update in a year or more is a risk, even with no known flaw today. Check each plugin's page on WordPress.org. If it shows a notice that it has been closed, treat it as urgent: closed plugins stop getting fixes and often close because of an unpatched security issue. Replace it, or remove it if nobody uses it. Delete deactivated plugins and unused themes (keep one default theme as a fallback), as the hardening guide advises. Deactivated code still sits on the server, and a vulnerable file can sometimes be reached directly.

PHP and database versions

WordPress.org currently recommends PHP 8.3 or greater and MySQL 8.4 or MariaDB 10.11 or greater. Older PHP versions still run WordPress, but they are past end of life and no longer get security fixes from the PHP project. Check the PHP version in Tools > Site Health > Info > Server. If a client is on an old version, plan the upgrade on staging first: PHP jumps tend to surface deprecated code in older plugins (our PHP 8.5 deprecated warnings guide covers what that looks like).

Vulnerability advisories

Updates fix what vendors have patched. Advisories tell you about flaws that are public, sometimes before a patch exists. Once a month, check your installed plugin list against a vulnerability database such as Wordfence Intelligence, WPScan or Patchstack. Many security plugins do this for you and flag a vulnerable version on the dashboard. If a plugin has a public flaw with no fix, deactivate it, replace it, or add a firewall rule and get the client's sign-off on the risk. Core security releases, like the WordPress 7.1.4 upgrade window fix, should reach every site within a day or two, not at the next monthly pass.

Staging first for anything risky

Agencies get burned by updates more often than by hackers. For major versions, page builder updates, WooCommerce and PHP changes, update on a staging copy, click through the key pages and forms, then update live with a fresh backup in place. For small plugin updates on a simple brochure site, updating live right after a backup is a fair trade-off. Decide per site, in writing.

03Users, logins and access

Access creep is the most common finding in agency audits. Contractors finish a project and keep their admin login. A client's former marketing manager still has an Editor account. A test user from the build is still there. Every one of these is a password that nobody is watching.

Review every user with Editor or higher

  • Go to Users > All Users and filter by Administrator, then Editor and Shop Manager if WooCommerce is installed.
  • For each account, confirm a real, current person owns it. If nobody can say who it is, downgrade it to Subscriber first, then delete it once confirmed. When deleting, WordPress asks whether to attribute the user's content to another account. Pick a current user so posts are not lost.
  • Keep the number of administrators as low as possible. Most clients need Editor, not Administrator.
  • Check Settings > General: unless the site needs public sign-ups, Anyone can register should be unchecked and New User Default Role should be Subscriber. An attacker who flips the default role to Administrator and opens registration has a permanent back door.
  • Look for any username of admin. The hardening guide advises against it because it is the first name attackers guess.

With WP-CLI this takes seconds per site:

wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
wp user list --role=editor --fields=ID,user_login,user_email
wp option get users_can_register
wp option get default_role

Two-factor authentication

Every administrator should have two-factor authentication. This one control stops most stolen-password logins. If the site runs Wordfence, it is under Wordfence > Login Security, where each user scans a QR code into an authenticator app and saves recovery codes. Wordfence also lets you require 2FA for chosen roles, which is the setting to use on client sites so it does not depend on each person opting in. If you use a different security plugin, use its 2FA. The monthly check is simple: count administrators, count administrators with 2FA, and the two numbers should match.

Application passwords

Application passwords are revocable credentials for the REST API, added in WordPress 5.6. They are useful (many integrations, deployment tools and AI site tools use them), but they do not go through the normal login form, so they skip 2FA. They also do not show up in a basic user review. Each month:

  • Open Users > Profile (or edit each administrator) and scroll to Application Passwords.
  • Check each one has a clear name, a known purpose and a recent last-used date. Revoke anything unknown or unused.
  • If a site does not use any API integrations, you can turn the feature off entirely with a filter. Do not do this blindly: it breaks any tool that relies on it, including some maintenance dashboards.
wp user application-password list 1 --fields=uuid,name,created,last_used,last_ip

To disable application passwords on a site that does not need them, add this to a small must-use plugin:

add_filter( 'wp_is_application_passwords_available', '__return_false' );

Sessions and offboarding

When someone leaves the client's team or yours, deleting their WordPress user is only one step. Use this offboarding list:

  1. Delete or downgrade the WordPress user and reassign their content.
  2. Revoke their application passwords before deleting, so any tool using them stops working cleanly.
  3. Log out their active sessions. On their profile screen, Log Out Everywhere Else ends other sessions, or use wp user session destroy <user> --all.
  4. Remove their hosting, SFTP, database, Cloudflare, registrar and Google Search Console access.
  5. Rotate any shared password they knew. Shared logins are the reason this step exists. A password manager with per-person access makes it painless.

Access outside WordPress

The WordPress admin is not the only door. Once a quarter, list who can log into the hosting panel, SFTP or SSH, the database tool, the DNS provider and the domain registrar. Each of those can take the whole site down or redirect it, and they rarely get reviewed. Turn on 2FA for each account that supports it, and use SFTP or SSH instead of plain FTP, as the hardening guide recommends.

04Firewall, login protection and blocked paths

A web application firewall (WAF) filters bad requests before they reach WordPress. You can run one at the plugin level (Wordfence, for example), at the edge with Cloudflare, or both. The monthly check is not about setting it up again. It is about confirming it is still on and reading what it saw.

Is the firewall actually running?

  • In a plugin firewall, confirm the status is enabled and, for Wordfence, that it runs in extended protection mode so it loads before WordPress.
  • After a migration or host change, re-check. Plugin firewalls that load through a server setting often break silently when the file path changes.
  • If the site is behind Cloudflare, confirm the DNS records are still proxied (orange cloud) and your WAF rules are still active. A record switched to DNS-only exposes the origin server. Our Cloudflare security and DNS guide covers the rules worth having.

Read the numbers, look for changes

Note the blocked requests and failed logins for the month. The trend matters more than the raw numbers: a sudden jump means the site is being targeted. A spike in failed logins for one username tells you that username is known to attackers, so check it has 2FA.

Login attempts should lock out after a few failures, and a CAPTCHA or Cloudflare challenge on the login page helps when failed logins climb.

Paths that should not be public

Test these from outside each month (a browser in a private window or a quick script). You want a 403, 401 or 404, never a 200 with content:

PathWhy it mattersExpected
/wp-config.php.bak, /wp-config.php~, /wp-config.oldBackup copies of config files expose database passwords403 or 404
/.env, /.git/HEADLeftover deployment files can expose credentials and source code403 or 404
/wp-content/debug.logDebug logs leak paths, plugin names and sometimes data403 or 404
/xmlrpc.phpUsed for brute force and pingback abuse; block it unless Jetpack or an app needs it403 if unused
/wp-json/wp/v2/usersLists usernames to anyone401 or 403, or no usernames shown
/?author=1Redirects to a URL that reveals a usernameNo redirect to a username
/wp-content/uploads/Directory listing shows every file403, not a file list
Old error logs in the web root (for example error_log, php_errorlog)Leak server paths and errors404 (delete them)

A small shell loop does the whole table at once:

for p in /.env /.git/HEAD /wp-config.php.bak /wp-content/debug.log /xmlrpc.php /wp-json/wp/v2/users /wp-content/uploads/ /error_log /php_errorlog; do
  printf '%s  %s\n' "$(curl -s -o /dev/null -w '%{http_code}' https://example.com$p)" "$p"
done

The leftover error log is not a made-up example. Our own check found an old PHP error log in a site root serving a year of server paths to anyone who asked for it. It had been there since before the current build.

05Backups and the restore test

Backups are the one control that saves you when every other control fails. They are also the control most likely to be broken without anyone noticing. A green tick in a backup plugin is not proof you can restore.

Monthly backup checks

  • Both parts: the handbook is clear that you need the database and the files to fully restore a site. Confirm both are in the backup, including wp-content/uploads.
  • Frequency matches the site: the handbook suggests weekly for smaller, quieter sites and daily for busy ones. For a WooCommerce store, daily is the floor, and many stores need more often than that.
  • Off-site: at least one copy must live away from the server. A backup stored only on the same hosting account disappears with the account.
  • Retention: keep several restore points. The handbook suggests at least 3 to 5 recent backups in different locations. If malware sat unnoticed for two weeks, you need a backup older than that.
  • Latest run: check the date and size of the last backup. A backup that is suddenly much smaller than last month usually means something was excluded or failed.

The restore test

Once a month, pick one client site and restore its latest backup to a temporary staging site or a local install. Rotate through your sites so each gets a full restore test at least once a quarter. Check that:

  1. The home page and two or three inner pages load and look right.
  2. You can log in to the admin.
  3. Images load (uploads were included).
  4. The newest post or order is there, which proves the backup is current.
  5. A form submits.

Write down how long the restore took. That number is your real recovery time, and it is worth telling the client. Then delete the test copy, because forgotten staging copies are their own risk.

06Files, configuration and malware

This group catches both bad configuration and signs that someone is already inside.

Configuration

  • File editing is off. The hardening guide recommends turning off the built-in theme and plugin editor, so a stolen admin login cannot be turned straight into code changes. It is one line in wp-config.php.
  • Debug display is off on live sites. WP_DEBUG_DISPLAY must be false in production. If you need logging, write to a log file outside the web root or block it.
  • wp-config.php permissions are tight. The handbook recommends 755 for folders and 644 for files in general, and 400 or 440 for wp-config.php where the host allows it. Some shared hosts need 644; check with the host before going stricter.
  • Rotate the security keys and salts in wp-config.php after a suspected breach or a staff change. It logs everyone out, which is the point.
  • Security headers are present: HSTS, X-Content-Type-Options, X-Frame-Options or a frame-ancestors policy, and a Referrer-Policy. Check them with your browser's network tab or a header checker.
define( 'DISALLOW_FILE_EDIT', true );
define( 'WP_DEBUG', false );
define( 'WP_DEBUG_DISPLAY', false );

File integrity

WP-CLI can compare core and plugin files with the official copies on WordPress.org. This catches modified core files that a scanner might miss:

wp core verify-checksums
wp plugin verify-checksums --all

Premium plugins will show as unverifiable, which is expected; rely on your security plugin's file scan for those.

Then look for the classic signs of a compromise:

  • PHP files in uploads. wp-content/uploads should hold media, not code. Blank index.php files are normal; anything else needs a look.
  • New files in the site root you did not add, especially random names ending in .php.
  • Must-use plugins you do not recognize in wp-content/mu-plugins. Attackers like this folder because mu-plugins do not show on the normal Plugins screen.
  • Changes to .htaccess that add redirects to outside domains.
  • Unknown admin users or scheduled tasks (cron events) with odd names.
find wp-content/uploads -name '*.php' -not -name 'index.php'
ls -la wp-content/mu-plugins
wp cron event list --fields=hook,next_run_relative

Finally, confirm the security plugin's scheduled malware scan ran this month and closed with no open issues. If you find something that looks like an infection, stop the checklist and switch to incident mode. Our guide on what to do in the first 60 minutes after a hack walks through it.

07SSL, domain, DNS and email

This is the group almost every WordPress security checklist skips, and it is where some of the worst outages come from. A hacked plugin is a bad week. An expired domain or a hijacked DNS account can take the site and the client's email offline at the same time.

SSL certificate

  • Check the certificate expiry date. Auto-renewal fails more often than people think, usually after a DNS change or when a CDN sits in front of the site.
  • Flag anything that expires in under 21 days and has not renewed.
  • Confirm the whole site loads over HTTPS with no mixed content and that HTTP redirects to HTTPS. WordPress.org now lists HTTPS support as a requirement.
echo | openssl s_client -servername example.com -connect example.com:443 2>/dev/null | openssl x509 -noout -enddate

Domain and registrar

  • Check the domain expiry date and that auto-renew is on with a working payment card. Put the expiry date in your shared tracker.
  • Confirm the domain has a transfer lock (often shown as clientTransferProhibited in a WHOIS lookup).
  • Confirm the registrar account has 2FA and that the contact email is one the client still reads. A domain renewal notice going to an ex-employee's inbox is a common way domains lapse.

DNS records

Export the DNS zone each month and compare it with last month. Look for records nobody can explain, such as a new A, MX or TXT record; unexpected changes can mean a compromised DNS account. Remove records for cancelled services too, because a dangling subdomain can sometimes be claimed by someone else.

Email authentication: SPF, DKIM and DMARC

Contact forms, password resets and WooCommerce order emails all depend on email that inboxes trust. Google's email sender guidelines require every sender to Gmail accounts to set up SPF or DKIM, and bulk senders (5,000 or more messages a day to Gmail) to set up SPF, DKIM and DMARC. Even a small site benefits from all three, because they also make it harder for someone to send phishing emails that look like they come from the client's domain.

RecordWhat it doesMonthly check
SPF (TXT)Lists the servers allowed to send mail for the domainOne SPF record only; it includes the SMTP service the site uses
DKIM (TXT or CNAME)Signs messages so receivers can verify themThe selector the mail service gave you still resolves
DMARC (TXT at _dmarc)Tells receivers what to do with mail that fails, and sends reportsA policy exists; reports show no unknown senders

On the WordPress side, send site mail through an SMTP service or a transactional email provider rather than the server's default mail function, and confirm the plugin's test email arrives.

08Forms and spam

Forms are a security surface and a reputation surface. Spam submissions fill inboxes, file upload fields can be abused, and a contact form that silently stopped sending means lost leads, which clients notice faster than any security alert.

  • Submit a real test through each important form and confirm the email arrives and the entry is saved. Do this every month. It is the single most useful check on this list for keeping clients happy.
  • Check spam protection is on: a honeypot field plus a challenge such as Cloudflare Turnstile or reCAPTCHA. Turnstile is a good default because most visitors never see a puzzle.
  • Review the spam folder count. A jump in spam usually means a bot found the form; tighten the protection. Zero entries for a month on a site that normally gets leads means the form may be broken.
  • Personal data: form entries hold names, emails and phone numbers. Delete old entries the client does not need, so a breach exposes less.

09The monthly client security report

None of the checklists we reviewed while writing this covered reporting, which is odd, because for agencies the report is what makes the work visible and what keeps clients paying for it. A client who never sees a report assumes nothing is happening. A client who gets a clear one-page summary every month understands what the care plan is for.

What to put in it

SectionWhat to includePlain-language example
StatusOne overall status: OK, Warning or Action neededAll checks passed this month.
UpdatesCore version, number of plugin and theme updates applied, anything held back and whyWordPress is current. [N] plugin updates applied, 1 held for staging testing.
SecurityScan results, blocked attacks, failed logins, any advisories that affected the siteThe firewall blocked [N] malicious requests. No malware found.
BackupsLatest backup date, retention, restore test result if this site was testedDaily backups are running. Restore tested on [date], took [N] minutes.
AccessUsers removed or added, 2FA coverageRemoved 1 former staff account. All admins use 2FA.
Domain and SSLExpiry datesSSL renews automatically. Domain renews [date].
Needs from youDecisions only the client can makePlease confirm whether the old events plugin is still needed.

White label reports

If you resell maintenance, the report should carry your agency's logo and voice, not your contractor's. If your white label partner does the checks, agree up front who sends the report and what goes in it. Our guide to what goes in a WordPress maintenance plan covers how to package this, and how to price care plans covers what to charge.

Running it across many client sites

Standardize the stack. When every client site runs the same security, backup and form plugins, every check and report works the same way.

Automate the collection, keep the judgment human. A management dashboard (ManageWP, MainWP and similar) or WP-CLI scripts can pull versions, updates, users, backup status and SSL dates for every site. Save human time for decisions: unknown users, odd DNS records, closed plugins, restore tests.

Decide who owns it. Either a named person on your team owns the monthly pass, or you hand it to a white label partner who does it under your brand. Our white label care plans run this kind of check from $25 per site per month (Essential: monthly updates, weekly backups, monthly security scans), $40 (Growth: weekly updates, daily backups, weekly scans) or $99 (Priority: daily scans and same-day response), with reports carrying your logo.

10The printable monthly WordPress security checklist

Copy this into your tracker. One row per site per month, and mark each line OK, Warning or Action.

GroupCheckDone when
UpdatesCore on the current releaseVersion matches the latest on WordPress.org
UpdatesPlugins and themes updatedNo update pending more than a week without a written reason
UpdatesPremium licenses activeLicensed plugins and themes show updates as available
UpdatesNo abandoned or closed pluginsEach plugin updated in the last year and not closed on WordPress.org
UpdatesInactive plugins and themes removedOnly one fallback default theme left inactive
UpdatesVulnerability advisories checkedNo installed version has an open advisory
UpdatesPHP version supportedPHP 8.3 or newer, or an upgrade is planned
UsersAdmin and Editor accounts reviewedEvery account maps to a current person
UsersRegistration and default roleRegistration off unless needed; default role Subscriber
Users2FA on all adminsAdmin count equals admins with 2FA
UsersApplication passwords reviewedEach has a known purpose and recent use
FirewallWAF on and loading firstStatus enabled; Cloudflare records proxied
FirewallBlocked requests and failed logins notedNo unexplained spike against last month
FirewallSensitive paths blockedEvery path in the table above returns 403, 401 or 404
BackupsLatest backup ran and is off-siteDate is current; size is normal
BackupsRetention3 to 5 or more restore points in more than one place
BackupsRestore test (rotating)Restored, checked and timed this quarter
FilesFile editing off, debug display offConstants set in wp-config.php
FilesCore and plugin checksumsverify-checksums passes, or differences explained
FilesNo PHP in uploads, no unknown mu-plugins or root filesOnly expected files present
FilesMalware scanLast scheduled scan finished with no open issues
SSL and DNSSSL certificateMore than 21 days left, or auto-renew confirmed
SSL and DNSDomainAuto-renew on, transfer lock on, registrar 2FA on
SSL and DNSDNS recordsNo unexplained changes against last month
SSL and DNSSPF, DKIM, DMARCAll three present and valid
FormsTest submissionEmail arrives; entry saved
FormsSpam protectionHoneypot plus Turnstile or reCAPTCHA on
ReportClient report sentStatus, updates, backups, access, decisions needed

When the checklist finds something

Sort findings into three buckets. Fix now: anything that looks like an active compromise, an exposed credential, or an expired certificate or domain. Fix this week: a missing 2FA, a closed plugin, a failed backup. Ask the client: anything that needs their decision or budget, such as replacing a plugin they paid for or upgrading hosting. If a site is already broken, our WordPress error fix service starts from $59 with a fixed quote.

11FAQ

How often should I do a WordPress security audit?

Run a short review every month and a deeper audit every quarter. Daily and weekly tasks such as backups, scans and updates should be automated, with alerts to a person. The monthly review covers what machines cannot judge: users, access, restore tests, DNS changes and client decisions.

What should a WordPress security checklist include?

At minimum: core, plugin, theme and PHP updates; a user and 2FA review; application passwords; firewall status; backups with a restore test; file integrity and malware scans; SSL and domain expiry; DNS and email authentication; form tests; and a short report of what was found and fixed.

Is a security plugin enough to keep WordPress secure?

No. A security plugin covers the firewall, login protection and scanning, but it cannot tell you a former contractor still has an admin account, that a backup no longer restores, or that the domain is about to expire. Those need a person working through a checklist.

Do I need Wordfence if I use Cloudflare?

They do different jobs. Cloudflare filters traffic at the edge before it reaches your server. A plugin firewall like Wordfence sees WordPress-specific context, such as which user is logging in, and also scans files. Many agencies run both. If you run only one, make sure login protection, 2FA and malware scanning are still covered.

How do I check if my WordPress site has been hacked?

Look for admin users you did not create, PHP files in the uploads folder, unknown must-use plugins, core files that fail wp core verify-checksums, redirects to spam sites, and warnings in Google Search Console. If you find any of these, stop and follow an incident response plan before changing anything else.

Should I change the wp_ database table prefix?

It can block some automated SQL injection attempts, so it is worth doing on a new build. On an existing site, changing it carries a real risk of breaking things for a small gain. Keeping plugins updated and running a firewall matters far more.

What do agencies include in a WordPress security maintenance plan?

Typically updates on a set schedule, daily or weekly off-site backups, malware scans, firewall and login protection, uptime monitoring, a monthly security review like this checklist, and a branded client report. Higher tiers add more frequent scans, faster response and restore testing.

Md Abu Jubaer Piash

Founder and lead WordPress developer, Finest Web Geek

Piash has built WordPress sites for agencies since 2013. He and his small team have shipped 800+ projects, most of them in Divi and Elementor, all under someone else’s brand.

  • MSc, Computer Science and Engineering
  • Top Rated Plus on Upwork
  • 800+ projects since 2013

How we write: every post comes from our own client work and is checked against the official docs. We update posts when the tools change.

Got a build on your desk right now?

Send the brief today and get a fixed quote by tomorrow.