WordPress flaws affect 351 plugins and four themes
WordPress vulnerabilities disclosed from October 26 to November 1, 2026 reached 549 issues across 351 plugins and four themes, according to Wordfence Intelligence. Of those flaws, 508 were listed as patched and 41 remained unpatched. The database credited 222 vulnerability researchers with contributions during the week, while Wordfence PRISM accounted for the largest listed total, with 59 vulnerabilities.
The severity breakdown included 17 critical, 132 high, 394 medium and six low severity vulnerabilities. Severity was measured using CVSS, the Common Vulnerability Scoring System, which assigns a score based on factors such as how a flaw can be reached and what an attacker could achieve. The volume matters because WordPress sites often depend on numerous separately maintained plugins and themes, so administrators must check every installed component rather than WordPress alone.
The most common weakness category was improper neutralization of input during web page generation, with 209 entries. Missing authorization accounted for 128, followed by deserialization of untrusted data with 35, improper handling of special elements in SQL commands with 31, and exposure of sensitive information to an unauthorized actor with 28. SQL, or Structured Query Language, is used to communicate with a website database. Other reported categories included improper authentication with 16, cross-site request forgery with 14, improper privilege management with 14, restricted-directory path problems with 12, dangerous file uploads with 12, improper control of code generation with 11 and authorization bypass through a user-controlled key with nine. Numerous other weakness types had between one and three entries.
Fourteen critical vulnerabilities received a CVSS score of 9.8. Bot for Telegram on WooCommerce through version 1.3.0 had an unauthenticated account-takeover route involving a fake Telegram webhook and a brute-forced login token; CVE-2026-109516 was still unpatched. A webhook is an automated message sent between online services when an event occurs. Patched 9.8 issues included arbitrary file uploads in Chat AI with Dispatcher through 2.3, Checkout Files Upload for WooCommerce before 2.4.0, Contact Form 7 versions 6.2 through 6.2.3, Contact Manager through 9.1.2, and Pie Register Premium through 3.8.4.0. An arbitrary file upload flaw can let an outsider place a file on the website without permission.
Other patched critical flaws included PHP object injection in Gravity Forms through 3.1.2, authentication bypass in Jupiter X Core through 4.61.0, account takeover in LogixFast Auth through 1.0.3, and PHP object injection leading to remote code execution in PDF Invoice for WooCommerce through 7.1.1. PHP object injection occurs when unsafe data is rebuilt as a software object and triggers unintended behaviour. Remote code execution means an attacker can make the affected server run commands. Project Manager through 4.1.1 also had an unauthenticated remote-code-execution flaw, while Qode Membership through 2.0.6.2, SimpleForm through 3.10.2 and Uncanny Toolkit for LearnDash through 3.8.2 had critical authentication or file-upload weaknesses. All three were listed as patched.
The remaining three critical issues scored 9.1 and were also marked patched. Acadlix LMS through 1.1.9 allowed unauthenticated arbitrary file deletion through the delete_file_data.file_path parameter. Popup Builder through 4.4.5 lacked authorization checks for moving arbitrary popup posts to the trash. WP Booking System through 2.1.0.5 lacked authorization around an AJAX action that removed calendar notes. AJAX is a way for a page to exchange data with a website without reloading the entire page.
Among the high-severity findings, WordPress Core versions 4.7.0 through 7.1.3 were affected by CVE-2026-119977, an unauthenticated remote-code-execution issue during an upgrade-window staged installation. It scored 8.1 and was listed as patched. Other patched 8.1 findings included an arbitrary file upload in the Avada theme through 7.16.2, administrator account takeover in Easy Digital Downloads through 3.7.2, PHP object injection in Enable Media Replace versions 4.1.4 through 4.2.2, account takeover in SureCart through 4.9.5, and PHP object injection in Ultimate Member through 2.13.1.
Several high-severity issues remained unpatched. These included PHP object injection in LeadSnap through 1.25 and the Royal Event theme through 2.0, account takeover in SSL Wireless SMS Notification through 3.8.1, SQL injection in SendPress Newsletters through 1.26.1 and Social Web Suite through 4.1.12, and arbitrary file reading in Lumise through 2.1.2. SQL injection is the insertion of database commands through input that a website fails to handle safely. Other unpatched 7.5 findings affected 10WebSocial, BuddyPress Xprofile Custom Field Types, Dynamic QR Code, Extra Fees for WooCommerce, News Kit Addons for Elementor and Social Snap.
Wordfence said it deployed new web application firewall rules for the WordPress Core flaw, unauthenticated remote code execution in The Grid through 2.8.1, and an unauthenticated arbitrary file upload affecting YOOtheme Pro versions 5.0.0 through 5.0.52. A web application firewall filters requests sent to a website. Two additional rules, WAF-RULE-968 and WAF-RULE-972, were redacted while work with the relevant vendors continued. Premium, Care and Response customers received the rules immediately, while the free version was scheduled to receive them after a 30-day delay.
Wordfence says its scanner notifies affected sites when enabled. Its vulnerability interface, API, Slack integration and HTTP webhook integration are free for personal and commercial use, and the API can provide a database dump covering more than 40,000 vulnerabilities. An API, or application programming interface, lets software retrieve and exchange structured information automatically. For organisations that prefer managed site infrastructure, AEU Hosting provides managed WordPress hosting secured end to end.
Site owners should inventory installed plugins and themes, compare their versions with the affected ranges, and install available updates promptly. Where an issue is still unpatched, removing or disabling the affected component is the clearest way to eliminate its exposed code until a corrected release is available. Administrators should also verify that backups can be restored before making major changes and continue monitoring vulnerability notices for newly published fixes.