You probably know which plugins your site runs. You may not know which exact versions are on disk, which inactive ones still sit in the plugins folder, or which premium add-on was installed from a zip file three years ago and never updated. Attackers work from that exact list. To check a WordPress site for vulnerabilities before they do, follow this sequence:
- Inventory every installed component down to its exact version.
- Match each version against a vulnerability database such as Wordfence Intelligence or Patchstack.
- Rank the findings by how easily each one can be exploited.
- Scan for signs the site is already compromised.
- Fix what you found, verify the fixes, and test a restore.
Plan on two to four hours for one site the first time. The difficulty is intermediate: you need admin and file access and the patience to read version numbers carefully, but no coding.
The pace of disclosure is why this matters now. On September 25, 2026, Patchstack's rolling 30-day display listed 1,425 WordPress vulnerabilities. Of those, 288 came from the Patchstack Alliance and 1,137 from other sources, so a check you ran last quarter is already stale.
The short version
List every plugin, theme, and piece of server software with its exact installed version. Check those versions against a vulnerability database. Deal first with anything that is unauthenticated, remotely exploitable, high severity, or unpatched. Then run an on-site scan for compromise, review admin accounts and file changes, apply fixes, rescan, and confirm you can restore from backup.
Prerequisites
- Administrator login to wp-admin
- SFTP, SSH, or host file-manager access to the WordPress directory
- Hosting control panel access, so you can see the PHP version, error logs, and backups
- WP-CLI, if your host provides it (it speeds up steps 1 and 6 considerably)
- A fresh backup stored somewhere other than the server
- A staging copy of the site, if you can create one
- A spreadsheet or audit document to record findings
Step 1: Build a complete software inventory
Record every piece of software on the site, including the parts that are switched off.
That means:
- WordPress core
- Every active and inactive plugin, plus must-use plugins
- Every theme, including parent themes and unused default themes
- The PHP version and web server software
- Externally loaded scripts such as tag managers, chat widgets, and CDN-hosted libraries
- Administrator accounts
- Scheduled tasks
- Configuration files such as wp-config.php and .htaccess
With WP-CLI, wp plugin list --fields=name,status,version and wp theme list give you the first two columns in seconds.
Give plugins and themes the most attention. In its State of WordPress Security in 2026 report, Patchstack found that 91% of vulnerabilities reported during 2025 were in plugins and 9% were in themes. WordPress core accounted for six. A review that stops at the core version on the Dashboard misses almost all of the risk.
The biggest gap in most inventories is what I call the directory blind spot. Premium plugins, commercial themes, and anything installed outside WordPress.org often don't appear in repository-based checks, so they get skipped. Put each one on the list with its vendor, its license status, and the date of its last update.
Tip: Record each plugin's slug (its folder name, such as `contact-form-7`), not its display name. Vulnerability databases index by slug, and display names often collide.
Step 2: Match exact installed versions against vulnerability databases
Look up each slug and its installed version in at least one vulnerability database, and log every matching advisory.
Your main options:
- Wordfence Intelligence: a free vulnerability database and API. It works for one-off manual lookups and scripted checks across many sites.
- Patchstack's database: covers similar ground and often lists issues from its own researchers.
- WPScan: offers a database and a command-line scanner that enumerates plugins from the outside.
The exact version matters because advisories apply to version ranges. "Up to date" only means you're on the latest release, and the latest release can still be vulnerable if the developer hasn't shipped a fix.
For an outside-in baseline before you log in, the Free plan from Wpaudit runs automated checks across selected core audit categories with no backend access or credit card needed. Treat the result as a starting point and still do the authenticated lookups, because an external scan can't see inactive plugins or files hidden behind wp-admin. The WordPress vulnerability scanner page explains what an external check can and cannot detect.
Premium components need a separate pass: read the vendor's changelog for entries labelled "security." When a changelog is vague about what it fixed, write that down too. Vague changelogs predict slow fixes.
Step 3: Rank findings by exploitability, not by alert count
Sort your findings so that the easiest-to-reach vulnerabilities sit at the top, whatever their total number.
I call this reachability-first triage. Work through the findings in this order:
- Unauthenticated and remotely exploitable. Anyone on the internet can trigger it.
- Actively exploited. Attacks are already happening elsewhere.
- Critical or high severity. Use the CVSS score, which is the scale NIST's National Vulnerability Database also uses.
- No patch available.
- Authenticated-only flaws, especially where your site has few registered users.
One unauthenticated high-severity flaw outranks ten medium issues that require a logged-in subscriber. Fix it first.
Volume makes this ordering necessary. Patchstack counted 11,334 new WordPress vulnerabilities reported in 2025, up 42% on 2024. Nobody patches that many issues in order of arrival, so you need a filter.
The same report estimated that 4,124 of those vulnerabilities, about a third, were serious enough to warrant mitigation rules. A narrower band of 1,966, or 17%, were high severity and likely candidates for automated mass exploitation.
That narrow band is also growing fastest. High-severity disclosures rose 113% year over year, according to Patchstack, and 2025 produced more of them than the two previous years combined. Posters on r/StopBadBots describe the practical result: when a widely installed plugin gets a high-impact disclosure, operators have hours, not weeks, before scanning bots arrive.
Step 4: Check maintenance status and supply-chain signals
Review whether each component is still maintained, even if no vulnerability is currently listed against it.
For each plugin and theme, check four things:
- The date of the last release
- Whether support forum threads get answered
- How fast past security issues were fixed
- Whether the plugin recently changed owners
Put a component with no release in a year and an unanswered support forum on the replacement list now. When a flaw is eventually disclosed, nobody will fix it.
Supply-chain risk now has an official response. In June 2026, WordPress.org announced an initiative called "Protect The Shire". It adds a delay of up to 24 hours before new directory plugin and theme releases go out through automatic updates, which gives reviewers time to catch suspicious releases. At the time of the announcement the directory held more than 78,000 plugins and themes and over 400 million installs. That scale explains why a single hijacked update is worth an attacker's effort.
Warning: The 24-hour delay covers the WordPress.org directory only. Premium plugins that update through a vendor's own license server get no such buffer, so check their changelogs yourself.

Step 5: Scan for signs the site is already compromised
Run an on-site malware scan in addition to the vulnerability checks you've already done.
Vulnerability scanning tells you what could be exploited. Malware scanning looks for evidence that something already was. A thorough review uses both, and it helps to choose tools by function rather than by brand.
| Tool | Main function | Published price |
|---|---|---|
| Wordfence Intelligence | Free vulnerability database and API | $0 |
| Wordfence Premium | On-site scanner and firewall | $149 per site per year |
| Patchstack Developer | Vulnerability intelligence and virtual patching | $69/month billed annually ($828/year) |
| MalCare | Separate prevention and malware cleanup tiers | Free $0; Protect $99; Repair $299; Fortify $499 (one site, annual) |
| WPScan | Vulnerability database and external scanner | See site |
Wordfence says more than 5 million websites use its Premium service, though that figure comes from the vendor.
A scan score is not the whole picture. Operators on r/Wordpress who have cleaned up hacked sites describe signs no scanner summarizes well:
- Generated gambling pages
- An unexplained user named "tester"
- Unfamiliar tag-manager or tracking code in the page header
SQL injection often leaves traces in the database instead: spam rows in wp_posts, unknown options in wp_options, or administrators created directly in wp_users. For a wider set of tests, see the WordPress security audit walkthrough.
Step 6: Review accounts, files, and scheduled tasks
Compare the site's accounts, files, and scheduled tasks against what should be there.
Start with these commands:
wp user list --role=administratorlists every administrator. Question every account nobody can explain.wp core verify-checksumscompares core files with the official release.wp plugin verify-checksums --alldoes the same for directory plugins.wp cron event listshows scheduled tasks. Look for jobs with random-looking hook names.
Then check for recently modified PHP files. On most Linux hosts, find wp-content -name "*.php" -mtime -30 lists anything changed in the last 30 days. Also open .htaccess and look for new redirect rules.
This is the step people skip, and they regret it later. Several r/Wordpress threads describe owners who discovered altered PHP files only after the site stopped loading, weeks after the change was made.
Tip: Save the output of each command with the date in the filename. Next month's audit then becomes a comparison against a saved baseline, and you have an audit trail that doesn't live in someone's inbox.
Step 7: Patch, remove, or virtually patch, then rescan
Apply fixes in this order:
- Update anything that has a patch.
- Delete anything you don't use.
- Replace anything abandoned.
- Use virtual patching only for components that have no fix yet.
Patches exist more often than people assume. In Patchstack's rolling 30-day display, 88% of listed vulnerabilities had a patch and 12% did not. Virtual patching, meaning a firewall rule that blocks the exploit pattern, covers that 12% while you wait. It reduces exposure but doesn't remove the flaw, so set a date to update or uninstall.
Keep core current too. WordPress 7.0.2, released July 17, 2026, fixed one critical and one high-severity vulnerability, with backports issued for 6.9.5 and 6.8.6. Adoption of major releases is fast: WordPress reported that more than half of sites moved to 7.0 within two weeks. That is a WordPress-reported figure rather than an independent measurement, and a lagging site stands out to attackers.
After patching, rescan. Confirm each version number on disk, then load the pages that depend on the updated components, especially forms and checkout.
Step 8: Test a restore before you close the audit
Restore your latest backup to staging and time how long it takes.
Scanners identify risk, but they can't recover a site after a successful attack. Only a backup you've tested and the logs that show what happened can do that. The r/Wordpress threads where a host has taken a site offline almost always come back to the same two problems: nobody knew the root cause, and nobody had tested a restore.
Confirm three things:
- Backups are stored off the server.
- The restore works.
- Access and error logs are kept long enough to trace an incident, which for most sites means at least 30 days.
The maintenance audit covers backup and site health checks in more detail.
Troubleshooting
Why does the scanner still flag a plugin I already updated?
Usually a second copy exists. Common places are a plugin bundled inside a theme, an old folder in mu-plugins, or a staging directory on the same server. Search the filesystem for the slug. Cached scan results are the other common cause, so force a fresh scan.
Why doesn't a premium plugin show up in any database?
Many commercial products are indexed poorly or not at all. Check the vendor's changelog and security page, subscribe to their release notes, and consider replacing any vendor that doesn't publish security fixes clearly.
What does "File should not exist" mean in a checksum check?
It means a file sits inside a core directory where no official release puts one. Some are harmless leftovers from old versions. Others are backdoors. Open each file before you delete it, and treat obfuscated code or eval() calls as signs of compromise.
What if an update breaks the site?
Roll back on staging, not production. Then report the break to the developer. Keeping the vulnerable version while you wait is a decision you should document, with virtual patching in place until a working fix arrives.
Next steps
Make the audit a recurring job with a fixed schedule: monthly for most sites, and weekly for anything that handles payments or logins. Keep the inventory in one format across all your sites so that a new disclosure takes minutes to check. The WordPress security checklist for 2026 covers the hardening steps that come after this, and the complete guide to auditing a WordPress website extends the process to performance and SEO.
Frequently asked questions
How do I check if my WordPress site has vulnerabilities?
List every plugin, theme, and core version installed, then look up each exact version in a vulnerability database such as Wordfence Intelligence, Patchstack, or WPScan. Include inactive and premium components. Rank matches by whether they are unauthenticated, remotely exploitable, high severity, or unpatched, and fix those first before working down the list.
Is a security plugin enough to find vulnerabilities?
No, a security plugin alone leaves gaps. Plugins such as Wordfence scan and firewall the site, but they won't tell you that a component is abandoned or that a premium add-on is missing from their database. Pair the plugin with a manual inventory, maintenance review, account review, and a tested restore to cover what automated scanning misses.
What is the difference between vulnerability scanning and malware scanning?
Vulnerability scanning finds software that could be exploited, such as an outdated plugin with a known flaw. Malware scanning looks for evidence the site has already been compromised, such as injected code, rogue files, or spam pages. A thorough review runs both, because a clean malware scan says nothing about the flaws still waiting to be exploited.
How can I tell if my WordPress site has been hacked?
Look for administrator accounts nobody recognizes, pages you didn't publish (gambling spam is common), unfamiliar tracking scripts, redirects added to .htaccess, and PHP files modified recently without explanation. Running `wp core verify-checksums` flags altered core files. Search Console warnings and visitor complaints about redirects are also strong signals.
How often should I audit a WordPress site for vulnerabilities?
Monthly is a reasonable minimum for most sites, and weekly suits sites that take payments or user logins. Also check immediately whenever a high-severity flaw is disclosed in a plugin you run. With over a thousand WordPress vulnerabilities appearing in a single 30-day window, quarterly checks leave too long a gap.
Related Reading
- 8 Best WordPress Security Audit Tools for Finding Hidden Threats
- 9 Best WordPress Audit Tools for Faster, Safer Websites
- How to Audit WordPress SEO and Performance Step by Step
- Parameter vs WordPress Audit: Key Differences for Site Owners
- WordPress Website Audit Pricing in 2026: What Businesses Should Expect
- White-Label WordPress Audit Reports: A Scalable Solution for Agencies
- 7 Best WordPress Audit Tools for SEO, Security, and Performance in 2026
- WordPress Audit vs Parameter: Which Website Analysis Approach Wins?
- WordPress Audit Tool: SEO, Security & Performance
- Features – Ultimate WP Audit
Free A free-forever plan for trying WP Audit with basic WordPress auditing capabilities.
