Wordfence recorded 498 vulnerabilities added to its database between November 2 and November 8, including issues in 313 plugins and one theme. Its November 12 WordPress vulnerability report says 41 remained unpatched, and 20 were rated critical.
For site owners, the useful first move is to check which listed products are installed, then confirm the affected and fixed versions in each vulnerability entry. The totals show the scale of disclosures in that week, but they do not tell you whether your particular site is exposed.
What the WordPress vulnerability report counted
Wordfence classified 457 of the 498 vulnerabilities as patched and 41 as unpatched when it published the report. That split is a practical reason to check your own plugin and theme inventory rather than treating the overall number as a direct measure of risk to every WordPress site.
The report’s severity breakdown was 6 low, 353 medium, 119 high and 20 critical. Medium issues made up the largest group. The figures describe Wordfence’s classifications for the vulnerabilities it added during the reporting week; they do not establish that all issues had the same exposure or required the same response.
| Report measure | Count |
|---|---|
| Total vulnerabilities | 498 |
| Patched | 457 |
| Unpatched | 41 |
| Critical severity | 20 |
| Plugins affected | 313 |
| Themes affected | 1 |
Input handling and authorization led the categories
Wordfence grouped the reports by weakness type. Improper neutralization of input during web page generation led with 179 cases, followed by missing authorization with 109. The next most common categories were improper privilege management, with 29, and improper control of code generation, with 28.
Those labels help describe the kinds of defects found, but they are not a substitute for reading an individual advisory. A weakness category alone does not identify the affected plugin version, whether a fix is available, or what permissions an attacker would need. Site owners should use the entry for each installed component to check those details.
Wordfence also listed one new firewall rule, WAF-RULE-976. The report says the affected data was redacted while Wordfence worked with the vendor on a patch. It does not name the product or describe the vulnerability, so the published information does not support a more specific assessment of that issue.
What site owners should check now
Start with the report’s list of affected software and compare it with the plugins and themes active on your site. For any match, open the corresponding vulnerability entry and check its affected versions, patch status and remediation details. Then update to a fixed release where one is available.
For an issue marked unpatched, the report’s aggregate count is not enough to decide what protection applies. Check the advisory for its specific details and watch for a vendor fix. Wordfence says its Premium, Care and Response customers received the new firewall rule immediately, while free users would receive that enhanced protection after a 30-day delay. That timing applies to the rule described in this report, not automatically to all 41 unpatched vulnerabilities.
Wordfence describes its vulnerability interface, API and webhook integration as free to use. Those tools can help teams review vulnerability data, but the immediate task for a site owner is simpler: identify whether an affected component is installed and whether its version needs attention.
FAQ
How many vulnerabilities did Wordfence report?
Wordfence reported 498 vulnerabilities added to its database for November 2–8, 2026. They affected 313 plugins and one theme.
How many were still unpatched?
The report lists 41 as unpatched and 457 as patched. Check each vulnerability entry for the affected software and any remediation details.
What should I do if my site uses an affected plugin?
Check the advisory for affected versions and available fixes, then update if your installed version is affected. If the report marks an issue unpatched, follow the vendor’s advisory for updates rather than assuming the general firewall note covers it.
Next step: compare your installed plugins and themes with Wordfence’s November 2–8 list, then verify the version and patch status of every match.