Security · Guide
How to Check a WordPress Plugin for Known Vulnerabilities
Short answer
To check a WordPress plugin for known vulnerabilities, note its exact name and version, then search that name in WPScan, Patchstack and Wordfence Intelligence and compare your version with each affected version range. If your version falls inside a listed range, update to the fixed version, replace the plugin, or remove it if no fix exists.
Key takeaways
- A known vulnerability means a flaw has been disclosed and listed in a public database, not that your site was hacked.
- Match your exact installed version against the affected version range, because a fixed version can share the same plugin name.
- WPScan listed 94,710 WordPress core, plugin and theme vulnerabilities as of November 2026.
- A CVSS score of 9.0 to 10.0 is Critical, 7.0 to 8.9 is High, 4.0 to 6.9 is Medium, and 0.1 to 3.9 is Low.
- Wordfence free users get new malware signatures 30 days later than Premium users, so a second database check still helps.
- A clean scan does not prove a site is clean, because a remote scanner cannot see files that stay on the server.
What does a known vulnerability mean for a plugin?
A known vulnerability is a security flaw in a plugin that has been found, disclosed and listed in a public database.
A plugin vulnerability is a defect in code that lets an attacker do something they should not be able to do, such as read data, change content or take over an account. The word known matters because the flaw is already public. Attackers can read the same database entries you can.
A vulnerable plugin does not prove your site was hacked. It means your installed code matches an affected version. You still need to check for signs of tampering, such as new admin accounts, strange redirects or changed files.
What do you need before you start checking?
You need admin access to WordPress, a list of your plugins with exact versions, and a backup made before you change anything.
Start with a full backup, because an update can break a feature or a theme link. If you need steps for that part, see how to back up WordPress. Keep the backup until you have checked the site after the fix.
You also need the exact plugin name, the folder name under wp-content/plugins, and the installed version number. A search by name alone is not enough, because two plugins can share a similar name. Write down each version before you search any database.
Allow about 30 to 60 minutes for a small site with under 20 plugins. A large site with 50 or more plugins can take 2 hours or more, because you must check each plugin and read each match.
How do you list every plugin and its exact version?
Open Dashboard, then Plugins, then Installed Plugins, and read the version number shown under each plugin name.
WordPress lists plugins in alphabetical order on the Plugins screen. The description under each name shows the version number, the author name and a link to the plugin site, according to the WordPress.org Plugins screen guide.
Use the filters at the top of the list to work in order:
- Click “All” to see every installed plugin.
- Click “Active” to list only plugins that run on the site.
- Click “Inactive” to list plugins that are installed but turned off.
- Click “Update Available” to list plugins with an upgrade in the WordPress Plugin Directory.
The Plugins menu also shows a balloon with a number when updates are waiting. That number tells you how many plugins need an update, according to the same WordPress.org Plugins screen guide.
Inactive plugins still need a check. Code on the server can still be reached in some setups, even when a plugin is turned off. Delete an inactive plugin you no longer use instead of leaving it in place.
How do you check a plugin in WPScan, Patchstack and Wordfence?
Search the plugin name in each database, then compare your installed version with the affected version range in each entry.
Use all three databases, because no single list holds every disclosure. Start with the WPScan database, which listed 94,710 WordPress core, plugin and theme vulnerabilities as of November 2026. Search by plugin name, open each entry, and read the affected versions, the CVE number and the fixed version.
Next, search the Patchstack database. Each row names the affected software, the flaw type, a risk score and the disclosure date. On 19 November 2026, it listed WP Duplicate up to version 1.1.11 with an unauthenticated file upload flaw scored 10.
Then search Wordfence Intelligence. You can search by CVE ID, software name or slug, or researcher name. Its API is free to query for personal and commercial use, according to Wordfence.
| Database | What to search | What each entry shows |
|---|---|---|
| WPScan | Plugin name or slug | Affected versions, CVE, fixed version |
| Patchstack | Plugin name | Flaw type, risk score, disclosure date |
| Wordfence Intelligence | CVE, name or slug | CVE, CVSS score, researcher, date |
If your version falls inside a listed range, that entry applies to you. If your version is above the fixed version, that entry does not apply. When two databases disagree on a version range, trust the newer entry and the plugin changelog, then recheck after the next update.
How do you read a CVE, a CVSS score and an affected version range?
Read the CVE as the flaw ID, the CVSS score as its severity from 0.0 to 10.0, and the version range as the test for whether your install is affected.
A CVE ID, such as CVE-2026-92084, is a public label for one disclosed flaw. In the Wordfence Intelligence database, that ID belongs to an unauthenticated shortcode flaw in Beaver Builder Page Builder up to version 2.11.0.5, with a CVSS score of 9.1 and a date of 2 October 2026.
CVSS is an open framework for rating severity, and its Base score runs from 0.0 to 10.0, according to FIRST, which maintains CVSS. The bands in the FIRST v3.1 specification are Low from 0.1 to 3.9, Medium from 4.0 to 6.9, High from 7.0 to 8.9, and Critical from 9.0 to 10.0.
The version range is the part that decides your next step. An entry that says “up to and including 2.11.0.5” affects version 2.11.0.5 and every version below it.
An entry that says “before 3.2.4” affects 3.2.3 and below, but not 3.2.4. Always check whether the range uses “up to”, “before”, “through” or “less than”, because each word changes the last affected version.
Also read who needs a login for the flaw. An unauthenticated flaw can be used without an account, so it ranks above an authenticated flaw with the same score. A flaw that needs an admin login still matters, but it is less urgent on a site with few trusted admins.
How do you use Wordfence Scan on your own site?
Install Wordfence, open Wordfence, then Scan, then click Start New Scan, and read each result by severity.
Wordfence Scan examines all files on your site for malicious code, backdoors and shells, and it also checks known malicious URLs, according to the Wordfence Scan help page. A scan takes from 1 minute to over 10 minutes, depending on how many files, posts and comments your site has.
Follow these steps:
- Go to Plugins, then Add New Plugin, search for Wordfence, then install and activate it.
- Open Wordfence, then Scan, and review the scan type before you start.
- Choose Standard Scan for most sites, or High Sensitivity if you think the site may already be hacked.
- Click “Start New Scan” and leave the page open until the scan reports completion.
- Read the results from Critical down to Low, and open each vulnerable plugin result first.
The Vulnerability Scan stage checks for out-of-date, abandoned and vulnerable plugins, themes and WordPress versions, according to the same Wordfence Scan help page. If you need the firewall side as well, see how to set up the Wordfence firewall.
Note the free tier limit. New malware signatures reach free users 30 days later than Premium users, according to Wordfence. That delay is one more reason to check WPScan and Patchstack by hand for a plugin you suspect.
How do you check a plugin without installing a scanner?
Use the plugin changelog, its WordPress.org page, and a remote scanner, then confirm the version by hand.
Open the plugin page on WordPress.org and read the changelog for the latest version. A security fix often appears as a short line, such as “Security: fixed a flaw in file uploads.” Compare the fixed version in that line with your installed version.
Then run a remote check at Sucuri SiteCheck. It is free, and it checks a URL for known malware, viruses, blacklist status, website errors, out-of-date software and malicious code. Enter your domain, read the result, and note any plugin it names as out of date.
A remote check has a clear limit. Sucuri states that its scanner only sees what is visible at browser level and will not detect anything on the server side. A clean SiteCheck result does not prove the site is clean, and it does not list every installed plugin.
For a plugin sold outside WordPress.org, use the vendor changelog and support page instead. A manual ZIP install shows an update notice only if the author includes a built-in updater, according to the WordPress.org Plugins screen guide. If no notice appears, check the vendor site for the latest version.
What should you do when a plugin is vulnerable?
Update to the fixed version first, replace the plugin if no fix exists, and remove it if you no longer need it.
Work in this order:
- Back up the site if you have not done so already.
- Update the plugin from Dashboard, then Plugins, then Installed Plugins, or from the Dashboard updates page.
- Recheck the version number after the update, and confirm it is at or above the fixed version.
- If no update exists, deactivate the plugin and look for a maintained replacement with the same job.
- If the plugin has no replacement and no fix, delete it and remove the feature it provided.
Do not download a copy from a random file site or a nulled plugin site. Those copies can carry added code, and they will not get updates from the author. Read are nulled WordPress plugins safe before you use any copy from outside the official source.
If the plugin was closed on WordPress.org, check what that means before you act. See what happens when a plugin is closed on WordPress.org. A closed plugin can return after a fix, but you should not wait on a plugin your site needs each day.
How do you confirm the fix worked?
Recheck the version, rerun the database search, and rerun your scanner, then look at the site.
Start on the Plugins screen and confirm the version number now matches the fixed version from the database entry. A version number that did not change means the update did not run, even if the dashboard no longer shows a notice.
Search the plugin name again in WPScan and Patchstack. The same entry should now show your version as outside the affected range. If the entry still lists your version, you updated the wrong plugin or the update rolled back.
Then rerun Wordfence Scan and check that the vulnerable plugin result is gone. Also open the front end of the site and test the pages that used the plugin, such as a form, a shop page or a gallery. If a feature breaks, restore the backup and try the update on a staging copy first.
Set a repeat check. Search your plugin list again each month, and after every WordPress core update. A plugin can be safe today and gain a flaw in a later release, so a single clean check does not last.
What mistakes should you avoid?
Do not trust a version number you did not read, a clean scan alone, or a single database.
These errors show up often:
- Checking the plugin name but not the version, so a fixed install looks vulnerable or a vulnerable install looks safe.
- Treating a clean remote scan as proof the site is clean, when the scanner cannot see server files.
- Updating without a backup, then finding the new version breaks a form or a checkout page.
- Leaving an inactive plugin in place for years, even though it still needs a version check.
- Ignoring a low or medium score on a plugin that handles logins, payments or file uploads.
- Posting flaw details in public before a fix exists, which can put other sites at risk.
If you find a flaw that is not yet listed, report it in private. Contact the plugin developer first where possible, then email the WordPress Plugins Team, according to the WordPress reporting guide. Do not post the details in public while the issue is unresolved.
If a plugin has had no update for a long time, treat that as a separate warning sign. See how to find abandoned WordPress plugins and plan a replacement before the next disclosure lands.
Frequently asked questions
How often should I check my plugins for known vulnerabilities?
Check at least once a month, and again after every WordPress core update or plugin update. A plugin that is safe today can gain a flaw in a later release, so a single clean check does not last. Set a monthly repeat in your calendar and keep the list of plugin names and versions with it.
Does a vulnerable plugin mean my site was hacked?
No. A vulnerable plugin means your installed version matches a disclosed flaw, not that anyone used it. Check for signs of tampering, such as new admin accounts, strange redirects, changed files or spam pages. If you see those signs, back up what you can, ask your host for help, and get a cleanup check from a security specialist.
Is a free scanner enough to check my plugins?
A free scanner is a good start, but it is not enough on its own. Free tools can miss new flaws, and remote scanners cannot see files that stay on the server. Pair a scanner with a manual check of each plugin name and version in two public databases, and repeat the check each month.
What should I do if a vulnerable plugin has no fixed version yet?
Deactivate the plugin if your site can run without it, and look for a maintained replacement that does the same job. If the feature is vital, ask the developer for a fix date and limit who can use that feature in the meantime. If no fix and no replacement exists, delete the plugin and remove the feature.
Can I keep using a plugin with a low severity flaw?
You can plan it for your next maintenance window, but do not ignore it. A low score still means a real flaw, and its risk rises if the plugin handles logins, payments or file uploads. Update it when a fix is out, and check whether the flaw needs a login or can be used without one.
Should I report a plugin flaw I found myself?
Yes, but report it in private first. Contact the plugin developer through their stated security contact, and report it to the WordPress Plugins Team if the plugin is listed in the directory. Do not post exploit details in public while the issue is unresolved, because that can put other sites at risk.
Sources
- WPScan Vulnerability Database WPScan
- Open Source Vulnerability Database Patchstack
- WordPress Vulnerability Database Wordfence Intelligence
- Scan Wordfence
- Plugins screen WordPress.org
- Reporting Plugin Security Issues WordPress Developer Resources
- CVSS v3.1 Specification Document FIRST
- Sucuri SiteCheck Sucuri
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.
Thanks — we review requests within 3 business days.
