Administrator reviewing a WordPress vulnerability report and plugin update checklist at a desktop computer Administrator reviewing a WordPress vulnerability report and plugin update checklist at a desktop computer

WordPress vulnerability report logs 497 new disclosures

Wordfence’s October 23 report lists 497 vulnerabilities added to its database for the week of October 12–18. It breaks down patch status, severity, flaw types and researcher contributions.

Wordfence added 497 vulnerabilities affecting 327 WordPress plugins and 23 themes to its Intelligence Vulnerability Database for October 12–18. Its WordPress vulnerability report, published October 23, says 69 of those entries were unpatched and 23 were rated critical. For site owners, the immediate task is to check installed software against the report’s vulnerability data, not assume every disclosure affects every site.

The weekly report also records 428 patched entries and contributions from 218 vulnerability researchers. Those numbers make the report useful as a snapshot of disclosure activity, but they do not tell you whether a particular site is exposed. That depends on which plugins and themes it runs, their versions and the status of available fixes.

What the WordPress vulnerability report counts

The 497 entries were added to Wordfence’s database during the reporting week. They cover 327 plugins and 23 themes, not 497 separate products. The report does not break down how many vulnerabilities affected each plugin or theme, so the totals should not be read as a count of affected sites.

Wordfence lists 428 vulnerabilities as patched and 69 as unpatched. That distinction gives site owners a practical starting point: identify whether a reported issue matches software on the site, then check whether its developer has released a fix. The report’s totals alone do not identify which installed components need attention.

Severity totals

The report assigns 153 entries a high severity rating and 23 a critical rating. The other 321 are split between 315 medium-severity and six low-severity entries.

Severity is useful for prioritizing review, but it is not a complete measure of risk to an individual site. A high or critical rating does not by itself establish that a vulnerable component is installed, that the affected version is in use or that an attacker has exploited the flaw. Check the details for each matching entry before deciding what to update first.

Reported measureCount
Total vulnerabilities added497
Patched428
Unpatched69
Critical severity23
High severity153
Medium severity315
Low severity6

Cross-site scripting leads the listed flaw types

Wordfence’s breakdown by vulnerability type lists 159 cases of cross-site scripting, the largest category in the report. Missing authorization follows with 116. The next most frequent categories are SQL injection, with 34 entries, and deserialization of untrusted data, with 33.

The remaining categories are smaller, but still worth checking when they match software in use. The report lists 31 exposures of sensitive information, 22 cases of improper privilege management and 20 authorization bypasses through user-controlled keys. It also records 15 code-injection flaws and 11 unrestricted file-upload vulnerabilities.

These classifications describe the reported flaws; they are not a ranking of which weaknesses are most likely to affect any one site. A site owner should use the software name, affected versions and patch status in each relevant vulnerability entry to decide what applies. The category count is context, not a substitute for checking the specific advisory.

Wordfence reports 218 researcher contributors

Wordfence says 218 vulnerability researchers contributed to WordPress security during the week. Its report names Wordfence PRISM as the top contributor, with 40 vulnerabilities, followed by johska with 19 and Peter Tang with 16.

The figures show how many different contributors were involved in the disclosures added to the database. They do not indicate that every item was found in the same way or carried the same level of risk. For maintainers, the report’s scale is another reason to keep a clear process for receiving vulnerability reports and publishing fixes.

What site owners should do next

Start with an inventory of active plugins and themes, including their installed versions. Compare those products with relevant entries in Wordfence’s database, paying particular attention to unpatched issues and to whether a fixed version is available. The weekly summary is a guide to the reporting period, not a site-specific scan.

Wordfence also says its Threat Intelligence Team deployed enhanced firewall protection for three vulnerabilities during the week. Two rule entries remain redacted while the team works with vendors on patches; the third is described as PHP Object Injection in Comments. The report says Premium, Care and Response customers received the rules immediately, while free users receive enhanced protection after a 30-day delay.

That firewall information does not replace checking and updating affected software. Wordfence presents the rules as protection for specific vulnerabilities, while its report separately lists patch status. Site owners should use the software vendor’s update as the primary fix where one is available.

FAQ

How many WordPress vulnerabilities did Wordfence report?

Wordfence reported 497 vulnerabilities added to its database for October 12–18, 2026. They affected 327 plugins and 23 themes.

How many vulnerabilities were still unpatched?

The report lists 69 unpatched vulnerabilities and 428 patched ones. Check each relevant advisory for the affected software and whether a fixed version is available.

Which vulnerability type appeared most often?

Cross-site scripting led the report’s flaw-type breakdown, with 159 entries. Missing authorization was second, with 116.

Next step: review your active plugins and themes against the report, then update any affected software to a fixed version where one is available.

Leave a Reply

Your email address will not be published. Required fields are marked *