Security

How to Read a WordPress Plugin Vulnerability Report and Decide What to Do Today

A pencil-and-wash illustration of the front of an old pine kitchen cabinet fitted with a row of mismatched add-on knobs in brass, porcelain and wood, one knob near the center hanging loose and tilted on its screw, in soft window light, a visual for reading a plugin vulnerability report: one small add-on out of many that needs attention today

A plugin vulnerability report answers five questions in a few lines: which versions are affected, which version fixes it, what kind of flaw it is, who can use it, and whether anyone already is. Read those fields in order and most reports turn into a clear action within minutes.

Our guide to what a CVE is covered the scores that come with an alert and a triage order for any advisory. This post goes deeper on one task: reading a report from Wordfence, Patchstack or WPScan field by field, checking your sites, and choosing to patch, deactivate or virtual patch. The worked example is the Bricksforge flaw from our Bricksforge post.

The short version: compare your installed version with the affected range, not with the headline. Read the login requirement before the score. Treat any exploitation flag from a WordPress security vendor as real evidence. If no patched version exists, deactivate and remove the plugin. Use WP-CLI to answer "do we run it, and which version" across every site at once.

The fields in a plugin vulnerability report

The main WordPress sources use different labels for the same facts.

What you need Patchstack label WPScan label What to do with it
Affected versions Vulnerable version(s) In the title, such as “< 3.1.8.10” Compare with each site’s installed version
Fixed version Patched version / Patched in Fixed in The minimum to install, not always the target
Flaw type Classification, OWASP Top 10 Classification: Type, CWE Tells you what an attacker gets
Who can attack Required privilege In the title, such as “Unauthenticated” Decides how urgent it is
Severity CVSS, Patchstack priority CVSS A sorting aid, read after the fields above

Wordfence publishes the same facts in its own database. As the CNA for many plugin CVEs, its description and score often appear on the NVD record too.

Affected and patched versions: read the notation

This is the field that decides whether the plugin vulnerability applies to you at all. Each source writes the range its own way. For Bricksforge, all three describe the same set of versions:

  • Wordfence (via NVD): versions up to and including 3.1.8.9.
  • Patchstack: <= 3.1.8.9.
  • WPScan: < 3.1.8.10.

Those mean the same thing. A site on 3.1.8.10 or later is not affected by this CVE.

The patched version is the first release with the fix. It is not always the version to install. For Bricksforge, the vendor changelog shows a second upload issue fixed only in 4.0.1. The plugin vulnerability report could not tell you that. Open the changelog before you pick a target version.

Some ranges have a lower end too, such as a flaw added in 2.0 and fixed in 2.4. A site on 1.9 is not affected. Read both ends.

Vulnerability type: what each one means for a site

The type tells you what an attacker can do once they reach the flaw. These five cover most WordPress plugin reports:

  • Cross-site scripting (XSS). The attacker gets script into a page that runs in someone else’s browser, ideally an admin’s. Stored XSS, saved in the database, is worse than reflected XSS, which needs a crafted link.
  • Cross-site request forgery (CSRF). The attacker tricks a logged-in user, usually an admin, into sending a request they did not mean to send. It needs someone to click.
  • SQL injection (SQLi). The attacker gets their own text into a database query. That can expose user records, password hashes and form submissions.
  • Remote code execution (RCE) and arbitrary file upload. The attacker runs their own code on the server. This is the worst outcome. Bricksforge was an arbitrary file upload that led to code execution.
  • Broken access control. A feature skips the check for who may use it. Reports often say “missing authorization.” Impact ranges from minor setting changes to admin takeover.

The OWASP Top 10:2025 ranks broken access control first and lists CSRF under it, so sources may file CSRF either way.

Who can attack: unauthenticated, subscriber or admin

For most sites, this field matters more than the score. Each plugin vulnerability report names the lowest role that can trigger the flaw. WPScan’s Bricksforge list includes an "Authenticated (Subscriber+) Privilege Escalation" entry, for example. The plus sign means that role or any higher one.

  • Unauthenticated. Anyone on the internet. Automated scanners can find it. Highest urgency.
  • Subscriber+. Any logged-in user. WordPress describes a subscriber as somebody who “can only manage their profile.” If the public can register, treat this almost like unauthenticated.
  • Contributor+ or Author+. Someone who can write posts, such as outside writers.
  • Administrator+. Someone who already controls the site. Lower urgency, unless old admin accounts linger.

Read this field against your own settings. A subscriber-level flaw on a site with three staff accounts is a scheduled update. On a membership site with 5,000 accounts, it is not.

Severity scores and exploitation status

Read the scores last. Our guide on how to read a CVSS score covers the vector in detail. Expect the sources to disagree. Bricksforge scored 9.8 from Wordfence and WPScan, and 10 from Patchstack.

Patchstack adds its own rating, Patchstack Priority, launched in November 2023. It mixes CVSS with the flaw’s prerequisites, its type, the plugin’s popularity and attack monitoring. The three levels come with suggested timings:

  • High: expected to be mass-exploited or known to be exploited. Patch in 0 days.
  • Medium: could be used in targeted attacks. Patch within 7 days.
  • Low: not expected to be exploited. Patch within 30 days.

Exploitation status is the strongest signal in a plugin vulnerability report. When Wordfence or Patchstack says attacks have started, believe it. These vendors see the attack traffic. General signals often lag. Our EPSS guide shows how low the model scored Bricksforge while attacks were underway.

One caution on labels. Patchstack’s Bricksforge page shows "Known to be exploited! (KEV)". The NVD record carried no CISA KEV listing when we checked. Read a vendor’s flag as its own evidence, not a CISA listing. Our post on the CISA KEV catalog covers what a listing requires.

When there is no patch: closed and abandoned plugins

Some reports have no patched version because the plugin is unmaintained or the fix is late. Patchstack marks these "No update available." Its documentation advises using its firewall, or disabling and removing the plugin until an update ships.

A related case is a plugin closed on WordPress.org. The Plugin Handbook says the plugin page then shows "This plugin has been closed and is no longer available for download." One listed reason is "Security Issue." The reason is shown publicly only after 60 days. Further detail stays with the WordPress.org security team and the plugin authors.

So a closed plugin may hide a plugin vulnerability you cannot read about yet. Existing installs keep running, and with downloads closed there is no new version to update to.

For a plugin with no fix, remove it or replace it with a maintained one. Use a firewall rule only as a stopgap while you do.

How to check installed versions across sites with WP-CLI

The first question for any plugin vulnerability is whether you run the plugin, and which version. WP-CLI answers it in seconds. Useful commands from the wp plugin list documentation and related pages:

  • wp plugin list --fields=name,status,version,update_version,auto_update lists every plugin, including inactive ones.
  • wp plugin get bricksforge --field=version checks one plugin by its folder name.
  • wp plugin list --fields=name,wporg_status,wporg_last_updated flags closed plugins.
  • wp site list --field=url | xargs -I % wp plugin list --url=% loops over a multisite network.

The wporg_status field is worth a scheduled run. In the WP-CLI source, it returns active for a plugin listed on WordPress.org and closed for one that was listed and no longer is. It stays empty for plugins that were never there, such as commercial ones.

For separate client sites, WP-CLI’s config file supports SSH aliases, and aliases can be grouped. One command then runs against a list of sites. Add --format=csv and you have an inventory to search when the next plugin vulnerability lands.

Auto-updates for plugins

WordPress 5.5 added per-plugin auto-updates. According to the WordPress documentation, admins opt in plugin by plugin from the Plugins screen. WordPress runs auto-updates twice a day by default. It emails the site owner when updates succeed or fail.

From the command line, wp plugin auto-updates enable <plugin> turns it on and status shows the current setting. The auto_update column in wp plugin list shows "on" or "off" per plugin.

Auto-updates close the gap between a fix and your site. They do nothing when no fix exists. Commercial plugins such as Bricksforge update through the vendor’s license system, so confirm with each vendor that auto-updates reach them.

A common split for small teams: auto-update low-risk plugins, and update builders, commerce and membership plugins by hand after a staging test.

Deactivate, patch or virtual patch: choosing today

With the fields read, the decision follows.

What the report and your check show Today Next
Patch exists, exploited or unauthenticated Update now Check for planted files and new admin accounts
Patch exists, but you cannot update today Virtual patch, or deactivate Update within days, then remove the stopgap
No patch, plugin closed or abandoned Deactivate Delete it and replace it
Admin-only flaw, no attacks reported Schedule the update Review who holds admin accounts

A virtual patch is a firewall rule that blocks requests aimed at one known flaw. The plugin code stays unchanged. Patchstack issues these for High and Medium priority flaws. Other web application firewalls may have a rule too, so ask your vendor rather than assume. Our firewall primer covers the basics. A virtual patch buys time. It only works if the rule exists and runs on that site.

Deactivating stops the code from running, but the files stay. Delete any plugin you do not need.

Worked example: the Bricksforge plugin vulnerability report

Here is the Bricksforge report read field by field. Values are as of October 21, 2026, from the Patchstack entry, the WPScan entry and the NVD record.

Field Value Reading
Affected 3.1.8.9 and older Check every Bricks site
Patched 3.1.8.10 Vendor changelog says 4.0.1 fixes a second issue
Type Arbitrary file upload (CWE-434) Leads to code execution
Privilege Unauthenticated Anyone can attack
Scores 9.8 (Wordfence, WPScan), 10 (Patchstack), Patchstack priority High All Critical
Exploitation Patchstack saw attacks from October 7, 2026 Act today

Every field agrees: update to a 4.0.x release today, then check for planted files. WPScan also lists four earlier Bricksforge flaws from 2026, three of them unauthenticated. A site left on an early 3.1.8 release carries several of them.

Frequently Asked Questions

What is a plugin vulnerability report?

It is a database entry describing one flaw in one plugin: affected versions, fixed version, flaw type, login needed and usually a score.

Which source should we trust: Wordfence, Patchstack or WPScan?

Check more than one when it matters. They usually agree on versions and type but differ on scores and labels. The vendor changelog settles version questions.

What does “Subscriber+” mean?

Any logged-in user with the subscriber role or higher. On a site with open registration, that can be almost anyone.

Should we install the patched version or the latest version?

Usually the latest stable release. Later releases may close related issues, as Bricksforge 4.0.1 did.

What should we do if a plugin has no patch?

Deactivate and delete it, then replace it. A firewall rule can cover a short gap.

How do we find closed plugins on our sites?

Run wp plugin list --fields=name,wporg_status. A value of “closed” means the plugin was on WordPress.org and has been removed.

Should we turn on plugin auto-updates?

For most small plugins, yes. Test builders, commerce and membership plugins on staging first.

Is a virtual patch enough?

No. It blocks known attacks on one plugin vulnerability while you update. The vulnerable code stays until you update or remove the plugin.

Digital Matters

Security Desk