Flat vector illustration of WordPress plugin blocks being inspected for vulnerabilities

Auditing plugins comes down to three habits: know exactly what is installed and at which version, match those versions against a public vulnerability database, and remove anything that is unused or unmaintained. Almost every WordPress plugin vulnerability that gets exploited in the wild is already patched and publicly documented before attackers use it at scale. The work is inventory and discipline, not deep technical skill.

Why this matters for your website

WordPress core is maintained by a large team and updates itself by default. Your plugins are written by thousands of independent developers with very different release habits. That gap is where risk accumulates.

A vulnerable contact form or gallery plugin can give an attacker file upload, SQL injection, or administrator account creation on a site that is otherwise well configured. For a WooCommerce store this means card-skimming scripts injected at checkout. Plugins are third-party code you ship to your customers, which is why the OWASP Top 10 treats dependency risk as its own category.

Step 1: Build a real plugin inventory

You cannot patch what you have not listed. Produce one inventory with plugin name, current version, active or inactive, and the date of the last release.

From the dashboard

Go to Plugins → Installed Plugins. The version number sits under each plugin name. Click View details to see the last updated date and the WordPress version it was tested up to. Note inactive plugins as well; deactivated code still sits on disk and can still be reachable.

With WP-CLI

If you have SSH access, one command gives you a machine-readable inventory you can keep in a spreadsheet:

wp plugin list --fields=name,status,version,update,update_version --format=csv

Run wp plugin list --update=available before every maintenance window. On multisite, add --network to catch network-activated plugins.

Diagram showing how an attacker fingerprints plugin versions and matches them to a public vulnerability database
Takeaway: version strings in your page source are enough for an attacker to pick a known exploit.

What an outsider can see

Plugin versions leak without any login. Common disclosures include:

  • Asset URLs in the page source such as /wp-content/plugins/<slug>/js/app.js?ver=3.2.1
  • readme.txt and changelog.txt files left in the plugin folder, which state the version in plain text
  • Generator tags, REST API responses at /wp-json/, and inline CSS handles
  • Directory listing on /wp-content/plugins/ when the web server is misconfigured

View the page source and search for wp-content/plugins to see what you are publishing. Hiding version strings is cosmetic, not a fix, but it does slow down opportunistic scanning.

Step 2: Match versions against vulnerability databases

Two public databases cover WordPress specifically. Search each by plugin slug, then compare the listed affected version range with what you have installed.

  • WPScan maintains a WordPress-focused vulnerability database with plugin, theme, and core entries.
  • Patchstack publishes a searchable database of WordPress plugin and theme vulnerabilities.
  • NVD holds the CVE records referenced by both, with CVSS scoring and references.

Record the CVE identifier and the fixed version for anything that matches. If a fixed version exists, update. If the entry says the vulnerability is unpatched, deactivate and delete the plugin, then find a replacement.

Decision tree for deciding whether to keep, update, replace or delete a WordPress plugin
Takeaway: every plugin ends the month in one of four states — keep, update, replace, or delete.

Step 3: Spot abandoned plugins

Abandonment is the slow version of a vulnerability. Check each plugin's page on the WordPress Plugin Directory for these signals:

  • Last updated more than 12 months ago, with no changelog entries since
  • Tested up to a WordPress version two or more major releases behind
  • Support threads open for months with no developer reply
  • A directory notice that the plugin is closed or no longer maintained
  • Ownership transferred to an unknown account shortly before a large feature change

One stale signal is tolerable for a small, simple plugin. Two or more on anything handling forms, uploads, payments, or user accounts is a reason to migrate now rather than at the next incident.

Step 4: A hardening routine you can repeat

Treat plugins as a supply chain you own. Five rules cover most of the risk.

  • Remove what you do not use. Deactivate, confirm nothing breaks, then delete. Deleting removes the files; deactivating does not.
  • Enable auto-updates for trusted, low-risk plugins. Do this from the Plugins screen for utilities and small add-ons.
  • Test critical plugins on staging. Payment, membership, caching, and page-builder plugins get a staging update and a checkout or signup test first.
  • Apply least privilege. Few people need the Administrator role. Editors cannot install plugins, which removes an entire class of accident.
  • Verify the source. Install from the WordPress Plugin Directory or the vendor's own site. Never install nulled or repackaged premium plugins.

On plugin count: there is no magic number. Twenty well-maintained plugins are safer than six abandoned ones. Judge each by maintenance status and privilege, not by the total.

Monthly plugin audit checklist

  • Inventory refreshed — run wp plugin list or export the Plugins screen; pass when every plugin has a recorded version.
  • Updates applied — update all plugins with pending releases; pass when the update count is zero after staging tests.
  • Database check — search WPScan and Patchstack for each slug; pass when no unpatched entry matches your installed version.
  • Abandonment review — check last updated and tested-up-to; pass when nothing exceeds 12 months without a plan to replace it.
  • Unused removal — delete inactive plugins and unused themes; pass when the inactive list is empty.
  • Accounts review — list Administrator users; pass when every one is a current, known person with MFA.
  • External view — run an unauthenticated scan of the public site; pass when no known-vulnerable version is reported.

For the surrounding configuration work, see the WordPress security guide and the section on OWASP software supply chain failures.

How to check your own site

Manual review catches what you already know about. An external scan catches what your site publishes without your knowledge.

Scantinel (scantinel.ai) is an automated website security assessment platform that runs OSINT, network, and OWASP Top 10 web vulnerability tests against ownership-verified assets and delivers actionable, business-owner-legible reports.

The Essential scan is passive and finishes in minutes. It detects your CMS version and publicly visible plugin versions, matches them against known vulnerabilities, and also reports TLS configuration, security headers, cookie flags, and exposed common files. The Full scan, on assets whose ownership you have verified, adds a WordPress and WooCommerce deep scan using WPScan against its vulnerability database, plus supply-chain checks for exposed .git and .env files and outdated JavaScript libraries.

Neither is a penetration test, and scans are never destructive. Start with the free WordPress security check, or run a WordPress vulnerability scan when you need the authenticated depth.

Key takeaways

  • Plugins are third-party code with third-party maintenance habits; inventory them by name and version before anything else.
  • Public sources leak your plugin versions through asset URLs and readme.txt, so attackers can fingerprint you without logging in.
  • Check every slug against WPScan and Patchstack, record the CVE and fixed version, and update or remove accordingly.
  • Abandonment signals — no update in 12 months, stale tested-up-to, silent support threads — matter as much as an open CVE.
  • Delete unused plugins rather than deactivating them, and limit who holds the Administrator role.

Frequently asked questions

How do I know if a WordPress plugin is vulnerable?

Take the plugin slug and installed version, then search the WPScan and Patchstack databases for that slug. If an entry lists an affected version range that includes yours, you are vulnerable until you reach the stated fixed version. A vulnerability scanner that checks your public site against the same databases automates this for your whole plugin list.

Can hackers see which plugins I use?

Usually yes, without logging in. Plugin folder names appear in script and stylesheet URLs in your page source, and version numbers appear in ?ver= query strings and readme.txt files. Hiding those strings reduces noise from automated scanning, but patching is the only control that changes the outcome.

Should I delete inactive WordPress plugins?

Yes. Deactivating stops WordPress from loading the plugin, but the files stay on disk and some can still be requested directly over HTTP. Delete anything you are not actively using, and keep a backup so you can reinstall if a feature turns out to be needed.

Published June 2025 by the Scantinel Security Research Team. Always verify current advisories against primary sources: OWASP, NVD, and WPScan.