WordPress Plugin Vulnerabilities: How To Read A Finding
Sooner or later a tool will put a red number next to a client’s site: 4 security findings. The first reaction is alarm. The second, a few weeks later, is to stop reading them, because the number never seems to go down.
Neither is right. Most WordPress plugin vulnerabilities are dull to deal with, because one update closes them. A few are urgent. And a small number are awkward, because the fix doesn’t exist or won’t install, and those are the ones that sit on a site for a year.
A site a few years old with a dozen plugins will almost always show something. What matters is how few decisions sit behind the number.
Here’s how to read one, rank a list, and handle the four cases you’ll meet, whichever tool produces it. Findings are one of the seven items in our guide to how to monitor WordPress sites.
Key Takeaways
- A finding means an installed version has a published security hole. It doesn’t mean the site has been broken into.
- Read five things: the component, the affected versions, the fixed version, the severity and whether an attacker needs a login.
- High or critical, no login needed and a fix available means update the same day.
- There are four cases: the update works, the update refuses, no fix exists, or the plugin is bundled inside a theme.
- A list of 14 findings is usually four or five decisions. Group them by plugin before you count.
What Is A WordPress Plugin Vulnerability Finding?
A finding is a match between something installed on your site and a published advisory. The advisory says a plugin has a security hole in versions up to a certain number. Your site runs a version in that range. That match is the finding.
Three things follow.
It isn’t a break-in. Nobody has looked inside the site. The check compares a list of installed versions with a public database. A malware scan is the separate check that looks for damage already done, and our help article on malware scans explains that side. If a scan has found something, start with what to do when a WordPress site is hacked.
It’s public. Attackers read the same databases, and once a hole is published, automated scripts look for sites still running the affected version.
It applies to themes and WordPress itself too. Plugins account for most advisories, but an old theme or an old WordPress version produces findings the same way.
How Do You Read A Finding?
Every finding, whatever tool shows it, comes down to five parts. Read them in this order.
- The component. Which plugin, theme or WordPress version. An inactive plugin with a hole is still a risk, and the fix is to delete it.
- The affected versions. Usually “up to and including” a version number.
- The fixed version. The first version without the hole. This is the most useful line, because it turns a warning into an instruction: update to at least this.
- The severity. A word, and usually a score from 0 to 10 on the CVSS scale: 0.1 to 3.9 is low, 4.0 to 6.9 medium, 7.0 to 8.9 high, 9.0 and over critical.
- What the attacker needs. Some holes can be used by anybody on the internet. Others need an account on the site first, sometimes an administrator’s. The title often says so, with words such as “unauthenticated” or “contributor+”. In the CVSS vector, PR:N means no login is needed.
Most findings also carry a CVE number, a public reference for that one hole, handy for telling a client exactly what you fixed.
One detail catches people out. Some advisories arrive without a score, and some tools then show a severity estimated from the title. An advisory with no score isn’t a low one. Read the title.
FIRST, which publishes CVSS, describes the score as severity in general, to be weighed against your own setup. That’s the next step.
Which Findings Do You Fix First?

The ones anybody can use without logging in, where a fix exists. A critical hole that needs an administrator account is less pressing than a high one that needs nothing.
| Severity | Attacker needs | Fix available | When |
|---|---|---|---|
| High or critical | Nothing | Yes | Today |
| High or critical | Nothing | No | Today: remove or replace the plugin |
| High or critical | A low-level account | Yes | This week, sooner if the site has public sign-ups |
| Medium | Anything | Yes | The weekly update run |
| Any | An administrator account | Yes | The weekly update run |
| Low | Anything | Yes or no | Routine |
Sites with public registration move up a row. A shop where anybody can create an account has already handed attackers the low-level account the advisory asks for.
Before you count your list, group it by plugin. Fourteen findings across ten sites is often one plugin on several sites, WordPress itself on a couple, and a few oddities.
What Do You Do With Each Finding?
One of four things, depending on the case.
The Fix Exists And The Update Works
Most findings are this case. Back up, update, check. Across many sites, update that one plugin everywhere it’s installed, as in how to bulk update WordPress sites. The finding closes when the version moves out of the affected range.
The Fix Exists But The Update Refuses
The update is listed, you run it, and it fails. With a premium plugin it’s nearly always the licence, lapsed or never entered. WordPress can see the new version but isn’t allowed to download it, and often says “Automatic update is unavailable for this plugin.”
Retrying does nothing. Find who holds the licence, tell the client plainly that a security fix is blocked until it’s renewed, and put a date on it. If nobody will renew, replace the plugin.
No Fixed Version Exists
No fixed version, and no release in years. The author has usually gone, so there’s nothing to wait for. Work down this list:
- Does the site use it? If not, delete it. Deactivating it isn’t enough to rely on.
- Is there a maintained plugin that does the same job? Replace it, on a staging copy first.
- Is the feature needed at all? Old sites carry plugins nobody remembers asking for.
- If it must stay for now, write down why, tell the client the risk, and set a date to revisit.
The Plugin Is Bundled Inside A Theme
Some themes ship their own copies of plugins, typically a slider or a page builder. Those copies update only when the theme’s author releases a new bundle, and on an old theme that may be never.
If the theme’s own update doesn’t bring a newer copy, the site needs a new theme. That’s a project, not an update, so say so early.
What About Findings In WordPress Itself?
Read them as one instruction: update WordPress to the latest minor release of the version you’re on, or to the newest version.
An older WordPress version can show twenty advisories at once. That looks dreadful and is usually one fix, because minor releases exist to carry security and bug fixes. WordPress only officially supports its newest version, though. Fixes are copied back to older versions as a courtesy, not a promise, so a site several major versions behind needs a plan to move up.
A major WordPress version is a different job. Do it on a staging copy, one site at a time.
Where Does The List Of Findings Come From?
From a vulnerability database, read by a tool that knows what’s installed on your sites. Several databases cover WordPress, among them Patchstack, Wordfence Intelligence and WPScan. They overlap heavily and differ at the edges, so two tools can show slightly different lists for the same site.
How the main management tools offered it on their own sites on 13 November 2026:
- ManageWP listed Vulnerability Protection as a premium add-on at $2 per website per month.
- WP Umbrella included vulnerability monitoring in its per-site price, and sold a Security add-on with a firewall and virtual patching at EUR 2 per site per month.
- MainWP included a free Vulnerability Checker in its self-hosted dashboard.
- WP Manager, in the Oxyforge members area, lists findings for every site with the severity and the version that fixes each, and WordPress’s own advisories as one line. You still press Safe Update or Update. It doesn’t block attacks, and it only covers sites hosted on Oxyforge.
Without a tool, you search a public database for every plugin on every site. For three sites that’s an hour a month. For twenty it won’t happen.
Two limits apply to every source. No findings doesn’t mean safe, because an unpublished hole is in no database, and neither is custom code. And a plugin from an unofficial download site can’t be judged by its version number at all.
A Worked Example: Fourteen Findings, Four Decisions
Say you look after ten sites for a design studio’s clients and the list shows fourteen findings on eight of them.
- Group by component. A form plugin on six sites, one high finding each: file upload without logging in, fixed in the next version. WordPress itself on two sites, with six advisories between them. A gallery plugin on one site, medium, no fixed version. A premium slider on one site, high, fix available.
- Form plugin, today. High, no login needed, fix waiting. Update it on all six with a backup first. Six findings close.
- WordPress, this week. Both sites take the latest minor release in the weekly run. Six findings close.
- The slider, today. The update refuses, because the licence belongs to the developer who built the site. Email the owner the renewal link and an alternative.
- The gallery, this month. No fix, no release in three years, and only one gallery page. Rebuild it with WordPress’s own gallery block and delete the plugin.
Six close in a morning, six more in this week’s run, and the last two are with named people and dates. A healthy list isn’t empty. It’s owned.
What To Do Next
- Get a list. If no tool shows you findings, that’s step one.
- Group it by plugin before you react to the number. The weekly routine around it is in our guide to managing multiple WordPress sites.
- Fix today anything high or critical that needs no login.
- Give every stuck finding an owner and a date: the lapsed licences, the abandoned plugins, the bundled sliders.
- If your sites are hosted on Oxyforge, WP Manager lists the findings with the fixed version beside each, free on every plan on the pricing page.
FAQ
Does a vulnerability finding mean my site has been hacked?
No. A finding says the door is unlocked, not that anybody has come in. A malware scan checks for a break-in, so run both.
How quickly should I fix a plugin vulnerability?
A high or critical finding that needs no login, with a fixed version available, should be updated the same day. Medium findings, and ones that need an attacker to hold an account already, can go in the weekly run. A finding with no fixed version needs a decision, not a wait.
What do I do when there is no fixed version?
If the site doesn’t need the plugin, delete it. If it does, find a maintained replacement, because a plugin with a published hole and no fix has usually been abandoned.
What does the severity score mean?
Most advisories carry a CVSS score from 0 to 10: under 4 is low, 4 to 6.9 medium, 7 to 8.9 high and 9 or more critical. The score describes how bad the hole is in general. Whether it matters on your site also depends on whether the attacker needs a login.
Why are there so many WordPress plugin vulnerabilities?
There are tens of thousands of plugins, from large companies to one person in their spare time, and each adds code to the site. Most holes are fixed quickly. The risk sits on sites that never take the fixed version.