techcoff.com

WordPress Security Audit Checklist (2026) — Audit Your Site in 30 Minutes

WordPress security audit checklist — 30-minute printable checklist with free scans

Wordfence blocked 62,969 attacks targeting a single WordPress flaw in 24 hours — and most site owners never knew the flaw existed.

Your site can be under attack right now while everything looks fine. This WordPress security audit checklist fixes that blind spot: in 30 minutes, four free scanners and a few dashboard checks show exactly where your site stands — and every weak spot below links to a guide that fixes it.

Why This WordPress Security Audit Checklist Starts With a Version Check

On November 3, 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-119977 to its Known Exploited Vulnerabilities (KEV) catalog — flaws attackers are actively exploiting.

It is a race condition in the WordPress core updater: during an update, an unauthenticated attacker could swap in a malicious wp-config.php and run code on the server. It scores 8.1 (High) on the CVSS scale, affects WordPress 2.7 through 7.1.3, and was fixed in 7.1.4 on October 28, 2026, with backports to older branches.

Your audit starts with one number — your WordPress version. Open Dashboard > Updates. If you are not on 7.1.4 or your branch’s latest security release, update before anything else. Full breakdown: WordPress 7.1.4 security update: CVE-2026-119977.

Step 1: Run the 4 Free Scans (10 Minutes, No Login or Account Needed)

First, look at your site the way an attacker does — from the outside.

1. Sucuri SiteCheck — malware and blacklist check

Open Sucuri SiteCheck, paste your URL, and hit scan. It checks for malware, injected spam, defacements, outdated software, and blacklisting by Google Safe Browsing, PhishTank, and others.

A clean result is good news, but SiteCheck only sees what the public sees — server-side malware slips past it.

2. WPScan — known vulnerabilities in your plugins and themes

WPScan runs the WordPress Vulnerability Database, maintained since 2014 and updated daily. Search any plugin or theme to see if your version has a known flaw and which version fixes it.

This scan matters more than most owners realize: plugins accounted for 91% of new WordPress vulnerabilities in 2025, according to Patchstack’s State of WordPress Security in 2026 report — and the most dangerous one on your site is usually the one you installed two years ago and forgot.

3. Qualys SSL Labs — your TLS grade

Visit SSL Labs’ SSL Server Test and enter your domain. It grades your TLS/SSL setup from A+ to F — certificate chain, protocols, ciphers, and known attacks like Heartbleed and POODLE. Below an A means a real weakness: a padlock only proves traffic is encrypted, not that it is strong. Aim for A or A+.

4. securityheaders.com — your HTTP headers grade

Scott Helme’s securityheaders.com grades your HTTP security headers — Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. Most sites score D or F — nobody configured them.

If your score is low, the fix needs no plugin — our guide walks through it: How to Add Security Headers to WordPress.

Step 2: The Manual Checks Only a Logged-In Owner Can Do

Free scanners test the outside of your site. These checks test the inside — and they catch most real-world problems. All need admin access.

Users and roles: who actually has keys to your site?

Go to Users > All Users and check every Administrator account. Delete any you do not recognize and demote anyone who does not need full power. Still have an account named “admin”? Rename it — attackers guess it first. Every user should be a real person with the smallest role that lets them do their job.

Plugins and themes: the forgotten-door check

In Plugins > Installed Plugins, delete — not just deactivate — every plugin you do not use. Deactivated plugins still sit on your server and can still be exploited. Do the same for themes: keep your active theme and one default, and delete the rest. Then update everything left and replace any plugin not updated in over a year.

File permissions and wp-config.php: lock the safe

File permissions should be 755 for folders and 644 for files. Your wp-config.php — the file holding your database password — should be 440 or 400, readable only by the server itself. Fix these in your hosting file manager or via FTP — one wrong permission can hand an attacker your entire database.

Login protection: 2FA and brute-force defense

Turn on two-factor authentication (2FA) for your admin account — a stolen password alone should never be enough. Then confirm your login page is protected against brute-force attacks, the most common attack WordPress sites face. Our guide explains the no-plugin approach: How to Protect WordPress From Brute-Force Attacks.

Backups: the restore test most owners skip

A backup you have never restored is a hope, not a safety net. Check three things: a recent backup exists (automatic, daily, stored off your server), it holds both files and the database, and you can actually restore it — test that on staging at least once a quarter. If your setup fails any of these, fix it: How to Back Up a WordPress Site Without a Plugin.

Logs and odd behavior: the 5-minute detective check

Finally, look for signs something already happened: repeated failed logins, logins from countries you have never visited, and new admin accounts. Then view your homepage as a visitor and look for spam links, strange redirects, or content you did not write. If anything looks off, run the full diagnosis: How to Check If Your WordPress Site Is Hacked.

The WordPress Security Audit Checklist: Three Cadences

  • This week (full 30-minute audit): update core, plugins, and themes; run all four free scans; review users and roles; delete unused plugins and themes; confirm permissions (755/644) and wp-config.php (440/400); confirm 2FA for every admin; verify a recent backup off-server.
  • Monthly (15 minutes): re-run the four scans and compare grades with last month; update everything; review new accounts and login logs; replace abandoned plugins; re-check headers after theme or hosting changes.
  • Quarterly (30 minutes, deep pass): test a full backup restore on staging; review all file permissions from scratch; audit every plugin — if you cannot name what it does, remove it; clean up old FTP accounts, subdomains, and staging copies; scan your security log for patterns.

Your Printable WordPress Security Audit Checklist

Copy this table or print it — one row per check, one fix per problem.

AreaWhat to checkFix
Core versionVersion current?Update now — 7.1.4 guide
Malware & blacklistMalware or blacklist?Run Sucuri SiteCheck and clean up
Plugin vulnerabilitiesKnown plugin CVE?Check WPScan; update or replace
TLS/SSLTLS grade A or A+?Fix ciphers; re-test — SSL Labs
Security headersHeaders grade A?Add missing headers — headers guide
Users & rolesAdmins legit?Remove, demote, or rename accounts
Plugins & themesUnused or abandoned?Delete unused; replace abandoned
File permissions755/644, wp-config 440/400?Fix in file manager or FTP
Login security2FA on, brute-force blocked?Enable 2FA — brute-force guide
BackupsRecent backup off-server?Automate backups — backup guide
Restore testRestore tested?Test a restore on staging
Hack signsOdd logins or spam links?Diagnose — hacked-site guide

FAQ: WordPress Security Audit Questions, Answered

How do I audit my WordPress site security?

Start with the four free scans — Sucuri SiteCheck, WPScan, Qualys SSL Labs, and securityheaders.com. Then log in and check users, unused plugins, permissions, 2FA, and backups — about 30 minutes in total.

How often should I audit WordPress security?

Run the full audit monthly, a quick scan check weekly, and a deep pass with a backup restore test quarterly. Run an extra audit after a core update, a new plugin install, a hosting change, or news of a major flaw like CVE-2026-119977.

How do I check if my WordPress site is hacked?

Run Sucuri SiteCheck for malware and blacklist flags, then look inside: new admin accounts, unfamiliar files in uploads, spam links or redirects, and failed-login spikes. Our hacked-site diagnosis guide walks through the full cleanup.

What are the best free WordPress security scanners?

Sucuri SiteCheck (malware and blacklists), WPScan (known WordPress flaws), Qualys SSL Labs (TLS), and securityheaders.com (headers). Each is free, needs no account, and tests a different layer — use all four, because no single scanner sees the whole picture.

Conclusion: An Audit Is Not a Chore — It Is Your Early Warning System

The real payoff of this WordPress security audit checklist: next time a flaw like CVE-2026-119977 lands on CISA’s exploited list, you will not be guessing. You will know your version, grades, users, and backups — and the fix will be a 10-minute update, not a weekend of panic.

Run the audit today, schedule the monthly repeat, and never let your site’s security be a mystery again. For the full walkthrough, start with our pillar guide: How to Secure a WordPress Site Without a Plugin. Prefer a professional to run it? See our services or get in touch.

Leave a Comment