Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Guide

How to Run a WordPress Security Audit

Short answer

Run a WordPress security audit by listing every plugin, theme and user, then scanning with WPScan and Wordfence, checking file permissions and HTTPS, and fixing what you find before rescanning. Start with a backup, work through the list in order, and write down every finding. A full audit takes about an hour on a small site.

Key takeaways

  • A WordPress audit pairs an outside scan with an inside check of users, files and settings.
  • Patchstack counted about 12,000 new WordPress vulnerabilities in 2025, with 91% in plugins.
  • WPScan is free for non-commercial use, with 25 free API requests a day.
  • WordPress has six built-in roles, and the Subscriber role has only the read capability.
  • Fix in order: update, remove unpatched software, tighten logins, fix permissions, then rescan.

What is a WordPress security audit?

A WordPress security audit is a full check of a site for known weaknesses, from outdated software and weak logins to exposed files and bad permissions.

It has two parts. An outside scan looks at the site the way an attacker does, with no login. An inside check uses the dashboard to review users, files and settings that no outside scan can see.

The audit matters because most flaws sit in plugins, not in WordPress itself. Patchstack counted about 12,000 new WordPress vulnerabilities disclosed in 2025, with 91% of them in plugins, and 36% of them exploitable, according to its State of WordPress Security in 2026 report.

Patchstack also reports that a third of vulnerabilities never get a patch at all, and that the average time to update, test and patch a flaw is 120 days. An audit finds the flaws that are still sitting on your site during that window.

What do you need before you start?

You need an admin login, a fresh backup, and a free WPScan API token before you start the audit.

Make a full backup first, files plus database, and keep it off the server. The audit itself is read-only, but you will change settings and update software later, and a backup lets you undo a bad fix.

Get a free WPScan API token from wpscan.com. The free plan allows 25 API requests a day, which covers about half of all WordPress sites, according to the WPScan plugin page.

Set aside about an hour for a small site, and longer for a large one. Open a notes file and record every finding with its location, so the fix list is ready when the scan ends.

How do you inventory your software?

List the WordPress version, every plugin and theme with its exact version, and the PHP version, then check each one against a vulnerability database.

In the dashboard, open Dashboard, then Updates, and note the WordPress version. Open Plugins and record each active plugin, each inactive plugin and its version. Do the same under Appearance, then Themes.

WordPress 7.1.4 was released on 28 October 2026 as a security release, according to Wordfence. If your version is older, note it as the first fix.

Check your PHP version under Tools, then Site Health, then Info. WordPress.org recommends PHP 8.3 or newer, with MySQL 8.4 or MariaDB 10.11 or newer.

Delete anything you do not use. WordPress.org's hardening guide says to delete a plugin you are not using, since a deactivated plugin still has code on the server.

How do you scan for known vulnerabilities?

Run WPScan from the command line for the outside view, then run a Wordfence scan from inside WordPress for malware and changed files.

WPScan is a free scanner for non-commercial use that checks the WordPress version, installed plugins and themes, usernames and exposed files against its vulnerability database. Its database has existed since 2014 and is updated daily, and it holds tens of thousands of known flaws.

Install it as a Ruby gem with gem install wpscan, or run it in Docker. The WPScan documentation gives both routes. Then run a scan with your token:

wpscan --url example.com -e vp --plugins-detection mixed --api-token YOUR_TOKEN

The free plan counts one API request per WordPress version, plugin and theme. An average site has 22 installed plugins, according to WPScan, so a site with many plugins can use up the daily 25 requests in one scan.

Then run Wordfence from the dashboard. Its scanner checks core files, themes and plugins against the WordPress.org repository, and checks for more than 44,000 known malware variants. Its free Threat Defense Feed updates are delayed by 30 days, while paid plans get them in real time.

Note the WPScan WordPress plugin is no longer actively supported for non-enterprise customers. Use the command-line scanner above, or Jetpack Protect, which uses the same WPScan database.

How do you check users and logins?

Open Users in the dashboard, remove accounts nobody uses, and give every remaining account the lowest role that fits its job.

WordPress has six built-in roles, and the Subscriber role has only the read capability. Check the roles and capabilities page if a role looks wrong for what that person does.

Look for these problems:

  • Admin accounts that belong to people who left
  • Several admins when one would do
  • The username admin, which attackers try first
  • Accounts with weak or shared passwords
  • No two-factor authentication on admin accounts

Turn on two-factor authentication for every admin. WordPress core does not include it, so use a plugin or your host's option. Wordfence adds TOTP two-factor authentication and login CAPTCHA.

Check the default role for new users under Settings, then General. It should be Subscriber unless the site needs something else.

How do you check files and the database?

Check file permissions, look for files that should not be there, and confirm no backups or database exports are public.

WordPress.org's hardening guide gives the permission scheme: folders at 755, files at 644, and wp-config.php at 400 or 440. Check them in your host's file manager, and fix anything set to 777.

WPScan's own checks look for wp-config.php backup files, exported database files, debug.log files and code repository files, as listed on its plugin page. Any of those in a public folder is a finding.

Open your site's file list and look for PHP files in the uploads folder, unknown files in the root, and files with recent dates you do not recognize. Wordfence flags changed core files by comparing them with the WordPress.org repository.

The hardening guide also says to check the database user: it needs only SELECT, INSERT, UPDATE and DELETE for normal WordPress work. Ask your host if you cannot see those settings.

How do you check HTTPS and headers?

Open the site over HTTPS, confirm the padlock and the redirect, and run the free Qualys SSL Labs test.

First, check the certificate. Let's Encrypt certificates last 90 days and should be renewed every 60 days, according to the Let's Encrypt FAQ. Confirm the expiry date is in the future.

Then run the SSL Server Test at Qualys SSL Labs, a free service that performs a deep analysis of a server's SSL configuration. The test page is at ssllabs.com/ssltest.

Check the redirect. Open the plain address in a private window and confirm the browser ends up on the secure address. Then check the security headers in the guide to add security headers.

Record any mixed content warnings from the browser console. A page that loads scripts over plain HTTP is only half protected.

How do you fix what the audit found?

Fix in this order: update what has a patch, remove what has none, then tighten logins and permissions, and rescan to confirm.

The order matters because the most exposed flaws go first:

  1. Update WordPress core, then plugins and themes with available patches.
  2. Delete plugins and themes with no patch and no maintained replacement.
  3. Remove unused user accounts and turn on two-factor authentication.
  4. Fix file permissions and remove exposed backup and export files.
  5. Renew or replace an expired certificate and fix mixed content.

If a plugin has a known flaw and no patch, do not wait for one. Patchstack reports that 46% of vulnerabilities had no developer fix at the time they were made public, so an unpatched plugin may never get one.

Rescan with WPScan and Wordfence after the fixes. A finding that is still there after the fix means the fix did not work, and the scan proves it.

If the scan found malware, follow the guide to remove malware from WordPress before doing anything else.

How often should you audit?

Run a full audit every quarter, a quick scan every month, and a fresh audit after any major change.

CheckHow oftenTool
Vulnerability scanMonthlyWPScan or Wordfence
Plugin and theme updatesWeeklyDashboard updates
User and role reviewQuarterlyUsers screen
File permission checkQuarterlyFile manager
Full auditQuarterlyThis checklist
Backup restore testTwice a yearYour backup plugin

New flaws appear every week, so a clean audit today says nothing about next month. The Wordfence weekly report for 2 to 8 November 2026 added 497 vulnerabilities in 312 plugins to its database in one week.

Repeat the audit after a host move, a redesign, or a new plugin install. Any of those can open a gap the last audit never saw.

What mistakes should you avoid?

The common mistakes are scanning once and stopping, trusting one tool, and fixing flaws without a backup.

Avoid these five:

  • Running only an outside scan and skipping the user and file checks
  • Ignoring findings in inactive plugins, which still have code on the server
  • Keeping the WPScan plugin when it is no longer supported for your use
  • Updating everything at once with no backup to roll back to
  • Filing the report away and never fixing the findings

An audit that finds nothing to fix is a result, not a waste of time. It means the site is clean on that date, and the next audit starts from a known good state.

See the broader numbers in WordPress security statistics to compare your findings with the wider picture.

The same comparison is in website security statistics.

Frequently asked questions

How long does a WordPress security audit take?

A full audit takes about an hour on a small site with few plugins, and longer on a large site with many plugins and users. The WPScan part is the slowest, since the free plan allows 25 API requests a day and a large plugin list can use that up.

Can I audit my WordPress site for free?

Yes. WPScan is free for non-commercial use, and its free API plan allows 25 requests a day. Wordfence has a free version with a firewall and a malware scanner. Both are enough for a small site audit.

Is a plugin scan enough for a full audit?

No. A scan finds known flaws and changed files, but it cannot see weak passwords, bad permissions or exposed backups on its own. Pair the scan with the manual user, file and HTTPS checks in this guide.

What should I fix first after an audit?

Start with the flaws that need no login to exploit, then anything already being attacked, then high severity flaws with no patch. Update what has a patch, delete what has none, and rescan after each round of fixes.

How often should I run a security audit?

Run a full audit every quarter and a quick scan every month. Repeat the audit after a host move, a redesign or a new plugin, since any of those can open a gap the last audit never saw.

Sources

  1. Installing WPScan WPScan
  2. WPScan WordPress.org
  3. Wordfence Security WordPress.org
  4. Patchstack Patchstack
  5. Hardening WordPress WordPress Developer Resources
  6. FAQ Let's Encrypt
  7. SSL Server Test Qualys SSL Labs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test