On this page (6 sections)
Wordfence published its weekly WordPress vulnerability report covering November 9 to November 15, 2026. According to the Wordfence Intelligence report, 388 vulnerabilities were added to its database in a single week, affecting 288 plugins and 29 themes.
Anyone who runs a WordPress site, from a single blog to an agency managing dozens of installs, should care. The summary we have does not name individual plugins or rate their severity, so this article focuses on what the numbers mean and how to check your own exposure quickly.
What the report says
The available text of the report is a short summary. It states that 388 vulnerabilities were disclosed in 288 WordPress plugins and 29 WordPress themes during the week, and that 178 vulnerability researchers contributed. All of it comes from one publisher, Wordfence, which operates the database the figures refer to. No other outlet has independently covered this report so far.
- vulnerabilities added in the week (Wordfence)
- 388
- plugins affected
- 288
- themes affected
- 29
- researchers who contributed
- 178
What we do not know from this summary
The summary does not list plugin names, CVE identifiers, severity scores, affected or fixed versions, or whether any of the issues are being exploited. We will not guess at any of these. If you need that detail, open the full report on the Wordfence site and compare its entries with the plugins you run.
Why weekly volume matters for site owners
Most WordPress compromises start with a known flaw in a plugin or theme that was never updated, rather than a flaw in WordPress itself. With hundreds of disclosures each week, the realistic risk is falling behind on updates and carrying abandoned or unneeded plugins.
Your exposure depends on three things: which plugins and themes are installed (active or not), whether the installed version is one of the affected ones, and whether the flaw can be reached without logging in. Only the first is something you can check in minutes.
How to check your own exposure
Start with an inventory. The first command below lists every installed plugin with its status and version, so you can compare it against the Wordfence report or a vulnerability database. Run it from your WordPress root with WP-CLI; the output is a table of name, status, update availability and version.
wp plugin listThe next command does the same for themes. Inactive themes still sit on disk and can still be vulnerable, so check them too.
wp theme listTo see only what has a pending update, filter the plugin list. Any row returned is a plugin where a newer version is available.
wp plugin list --update=availableWhat to do now
- Take a backup of files and database before changing anything.
- Run the plugin and theme listings above and write down every name and version.
- Open the full Wordfence report and compare it against your inventory.
- Update any plugin or theme that has an available update, starting with ones that are internet-facing such as forms, membership, e-commerce and file upload tools.
- Delete plugins and themes you do not use, including inactive ones.
- Replace anything that is no longer maintained by its author.
- Check user accounts for administrators you do not recognize.
- Enable automatic updates for plugins you trust and that are updated regularly.
Detection and monitoring afterwards
If a plugin you run appears in the report and you updated late, look for signs of earlier abuse: new admin users, unfamiliar files in wp-content, modified core files, or unexpected redirects. Our guide on how to check if a website is hacked covers the steps, and website hacked: what to do applies if you find something.
For ongoing coverage, a recurring habit works better than reacting to headlines. Review updates weekly, subscribe to a vulnerability feed for the plugins you use, and consider a website firewall as an extra layer while patches roll out. Our WordPress security checklist lists the routine tasks.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
