← All articles

WordPress vulnerabilities: 497 flaws disclosed in one week

WordPress vulnerabilities: 497 flaws disclosed in one week

WordPress vulnerabilities rose to 497 disclosures during the week of November 2 to November 8, 2026, according to Wordfence Intelligence. The flaws affected 312 WordPress plugins and one theme, while 218 vulnerability researchers contributed findings. Wordfence added the disclosures to its Vulnerability Database, where site owners and organisations can check whether their installations are affected.

Of the 497 vulnerabilities, 457 were marked patched and 40 were unpatched. The severity breakdown included 21 critical, 118 high, 352 medium and six low severity issues. A critical rating indicates that the vulnerability can have a particularly serious effect, while the Common Vulnerability Scoring System, or CVSS, is the scoring method used to express that risk on a scale that includes ratings such as 9.8, 9.1 and 8.8.

The most common weakness was improper neutralisation of input during web page generation, with 179 cases. This category commonly includes cross-site scripting, or XSS, where harmful code can be stored or displayed through a website. The report also recorded 108 cases of missing authorisation, meaning a site did not properly check whether a user was allowed to perform an action, along with 29 cases of improper privilege management and 28 cases involving unsafe code generation. Other reported categories included exposure of sensitive information, authorisation bypass, SQL command injection, file upload problems, cross-site request forgery and server-side request forgery.

Several critical vulnerabilities allowed unauthenticated access, meaning an attacker would not need to log in first. BuddyForms versions up to 2.10.5 had a 9.8 privilege escalation flaw, CVE-2026-107622, and Contact Form 7 versions 6.2 through 6.2.3 had a 9.8 arbitrary file upload flaw, CVE-2026-114432. Both were marked patched. Patched critical findings also affected Fiber Admin 3.1.0 through 4.0.0, s2Member versions up to 260927, OAuth Single Sign On versions up to 7.1.3, payever WooCommerce Gateway versions up to 4.8.0, Printcart Store versions up to 2.13.2, Registration Form for WooCommerce versions up to 1.1.4, and Ultra Addons for Contact Form 7 versions up to 3.5.54.

The report marked several other critical flaws unpatched. They included unauthenticated remote code execution in Confection 0.4.0 through 0.4.7, CVE-2026-115252; WP Libre Form up to 1.5.0.1, CVE-2026-118423; and Static Snapshot up to 0.2.1, CVE-2026-116533. Remote code execution means an attacker may be able to make the website run commands of their choice. Unpatched critical findings also affected WP Duplicate up to 1.1.11, EASY-JS-WPAPI up to 2.0, Ecommerce Affiliate up to 1.0.0, Grand Job up to 1.2.1 and Wurdey up to 1.0.0. The listed issues included arbitrary file upload, administrator credential exposure, account takeover and privilege escalation.

High severity findings covered a wide range of popular site functions. LiteSpeed Cache up to 7.9.1 had a patched 8.2 issue involving disclosure of WooCommerce store API cart, checkout personal information and cart tokens through public REST caching. Advanced Custom Fields up to 6.8.10 had a patched stored XSS flaw. Elementor up to 4.3.5, wpDiscuz up to 7.6.73, Form Maker by 10Web, Flying Images, FV Flowplayer Video Player and several other plugins also had stored XSS findings, most of them marked patched. SQL injection, a flaw that can let hostile input manipulate database queries, was reported in SliceWP Affiliates, Amelia Pro, GS JWT Authentication, IVPAY payments, Mail Mage, Productive Commerce and wpForo Forum. The GS JWT Authentication, IVPAY payments and Mail Mage findings were marked unpatched.

Wordfence said its Threat Intelligence Team reviews vulnerabilities for impact, severity and the likelihood of exploitation. It deployed enhanced firewall protection for WAF-RULE-976, although the vulnerability data was redacted while work with the vendor on a patch continued. Premium, Care and Response customers received the rule immediately, while free Wordfence users were scheduled to receive the enhanced protection after a 30 day delay. The report does not identify the affected software in the redacted entry.

Wordfence also said its free Intelligence interface, vulnerability API and webhook integration are available for personal and commercial use. An API is a way for software to request data automatically, while a webhook sends an automatic notification when an event occurs. Enterprises, hosting providers and individuals can use the API to obtain a complete database dump containing more than 40,000 vulnerabilities, and use webhooks to receive new entries and database updates in real time. Wordfence said sites running its scanner should already have been notified when an installation was affected.

For site owners, the practical priority is to inventory every active plugin and the Soledad theme, compare installed versions with the affected ranges, and apply available updates without delay. Unpatched software should be disabled or removed where it is not essential, especially when a flaw permits unauthenticated access. A managed WordPress service such as AEU Hosting can help with the broader operational burden through managed WordPress hosting secured end to end, but site owners still need to confirm that their specific plugins and theme are supported and updated.

The disclosures came from a broad group of researchers. Wordfence PRISM contributed 25 findings, while mroccon contributed 13, and Kuba and Jacek Sowiński contributed 12 each. The report also credits researchers including Naoki Kawahigashi, UKO, AndrewN, Karthik Ramakrishnan and Peter Tang, alongside many other contributors. Responsible disclosure gives vendors an opportunity to release patches before or as technical details become widely available, but the 40 unpatched cases show why monitoring and rapid response remain necessary.

Also available in: DeutschItalianoShqip