
Wordfence Intelligence added 388 newly disclosed vulnerabilities last week across 288 WordPress plugins and 29 WordPress themes, underscoring how quickly the WordPress ecosystem can shift from routine maintenance to urgent patching. The weekly report for November 9, 2026 to November 15, 2026 also credits 178 vulnerability researchers for contributions to WordPress security during the period.
What the latest Wordfence Intelligence report shows
The weekly tally reflects a broad mix of issues, with most vulnerabilities already patched but a meaningful number still unpatched. Wordfence says 322 of last week’s disclosures were patched, while 66 remained unpatched at the time of the report.
Severity levels were weighted heavily toward mid-range findings, but the week still included a substantial number of severe issues:
- Low severity: 3
- Medium severity: 274
- High severity: 89
- Critical severity: 22
That distribution is a reminder that even when most disclosures are not immediately critical, a single vulnerable plugin or theme can create a serious risk if it is installed and exposed on a live site.
Common vulnerability patterns in WordPress plugins and themes
Wordfence’s breakdown by CWE category shows the kinds of coding flaws security teams encounter most often in WordPress software. The most common issue class last week was Improper Neutralization of Input During Web Page Generation, followed closely by authorization and access-control weaknesses.
The top CWE categories reported were:
- Improper Neutralization of Input During Web Page Generation: 117
- Missing Authorization: 86
- Exposure of Sensitive Information to an Unauthorized Actor: 28
- Cross-Site Request Forgery: 24
- Improper Neutralization of Special Elements used in an SQL Command: 17
- Improper Control of Generation of Code: 15
- Authorization Bypass Through User-Controlled Key: 14
- Improper Limitation of a Pathname to a Restricted Directory: 14
- Improper Privilege Management: 13
- Unrestricted Upload of File with Dangerous Type: 10
File upload flaws, authentication bypasses, and authorization bugs are especially important for site owners to monitor because they often map to direct compromise paths, including data theft, account takeover, and remote code execution.
Why Wordfence says this data is available for free
Wordfence says its mission with Wordfence Intelligence is to make vulnerability information accessible to the WordPress community so individuals and organizations can build layered defenses. The company says the Wordfence Intelligence user interface, vulnerability API, and webhook integration are all free for personal and commercial use.
The report also notes that enterprises, hosting providers, and individuals can use the vulnerability database API to receive a complete dump of the database, which now contains more than 40,000 vulnerabilities. The webhook integration can be used to keep pace with newly added vulnerabilities and database updates in real time, also free of charge.
For security teams that manage multiple WordPress environments, this kind of automated visibility can be the difference between reacting after an incident and patching before an exploit attempt lands.
Researchers behind the disclosures
Wordfence highlighted 178 researchers who contributed to WordPress security last week, with several names appearing multiple times near the top of the leaderboard. Among the most active contributors were AndrewN and Wordfence PRISM with 15 vulnerabilities each, followed by beopseong.kim with 14.
Other notable contributors included Naoki Kawahigashi and Karthik Ramakrishnan with 12 each, and Malvin Valerian Gultom, Jacek Sowiński (dzaku), and Benjamin Kincses with 11 each. Wordfence also credited a long tail of researchers who disclosed one or more issues during the week.
The report says researchers can also be featured in future weekly reports by responsibly disclosing WordPress vulnerabilities through Wordfence’s Bug Bounty Program, where in-scope findings may earn a bounty and a place on the Wordfence Intelligence leaderboard.
Examples of critical issues disclosed last week
Among the most urgent findings were multiple unauthenticated file-upload flaws and account-compromise bugs. These kinds of issues are often high priority because they can be exploited without a valid login, making them attractive targets if the affected software is installed and publicly reachable.
Some of the critical vulnerabilities listed in the report include:
- Advance Guest Post <= 1.9 — Unauthenticated Arbitrary File Upload, CVSS 9.8, unpatched, CVE-2026-118064, published Nov. 11, 2026.
- Advance Guest Post <= 1.9 — Unauthenticated Arbitrary File Upload, CVSS 9.8, unpatched, CVE-2026-118063, published Nov. 13, 2026.
- Ahime Image Printer <= 1.0.0 — Unauthenticated Arbitrary File Upload, CVSS 9.8, unpatched, CVE-2026-124833, published Nov. 11, 2026.
- Auth Armor – Passwordless Login <= 1.0.3 — Unauthenticated Account Takeover to Privilege Escalation, CVSS 9.8, unpatched, CVE-2026-110960, published Nov. 13, 2026.
- AutomatorWP Pro Webhooks addon <= 1.4.4 — Missing Authorization to Unauthenticated Arbitrary User Password Reset / Account Takeover via Webhook with “Is the user ID” field, CVSS 9.8, patched, CVE-2026-126173, published Nov. 13, 2026.
- Basel Post Types <= 1.18 — Unauthenticated Authentication Bypass via forged Opauth callback signature with hardcoded fallback salt, CVSS 9.8, patched, CVE-2026-89324, published Nov. 10, 2026.
- Chatterbug Forms <= 1.0.2 — Unauthenticated Arbitrary File Upload via public form submission, CVSS 9.8, patched, CVE-2026-125055, published Nov. 12, 2026.
- Cloud Storage Manager for Fluent Forms <= 1.2.0 — Unauthenticated Arbitrary File Write via Google Drive filename path traversal, CVSS 9.8, patched, CVE-2026-120522, published Nov. 14, 2026.
- Descope < 1.2.0 — Unauthenticated Account Takeover, CVSS 9.8, patched, CVE-2026-110959, published Nov. 12, 2026.
The report also begins listing further critical issues in products such as ELEX WordPress HelpDesk & Customer Ticketing System, showing that the week’s risk was not limited to a single plugin category.
What WordPress site owners should take from this
The practical takeaway is straightforward: review installed plugins and themes, confirm versions, and patch quickly when a vendor release is available. If you run the Wordfence plugin with scanning enabled, Wordfence says you should already have been notified if your site was affected by any of these vulnerabilities.
For teams that want real-time visibility beyond manual checks, Wordfence points to its Slack and HTTP Webhook Integration, which it says is free to use and designed to alert users whenever a vulnerability is added to the Wordfence Intelligence database.
In a WordPress ecosystem where new disclosures arrive every day, weekly reports like this one are less about counting bugs and more about reducing the window between disclosure and remediation. That window is where attackers often look for easy wins.
Source: Original report
Was this helpful?
Explore more: WordPress Troubleshooting More WordPress & CMS Tech News
Last Modified: November 20, 2026 at 10:32 pm
0 views

