Tracker · Exploited plugins · October 2026

Exploited WordPress plugins, October 2026: flaws and fixed versions

The plugin sections of the four October 2026 weekly briefings in one place, oldest first: the flaws each week’s sources marked as exploited or rated critical, what each one lets an attacker do, and the version that fixes it. Where an exploited label rests on a single source, the section says so. The Rank Math SEO PRO package and the Ninja Forms campaign from the same month have advisories of their own.

This page collects the plugin sections of the weekly briefings of 5, 12, 19 and 26 October 2026, oldest first. Each section is dated; a plugin listed in an earlier week stays on the list until its fix is installed.

5 October
Six plugin vulnerabilities, three flagged exploited by Patchstack
12 October
Eight critical plugin flaws, all exploitable without a login
19 October
Four flaws under exploitation, plus LearnPress and WP Booking System to patch
26 October
Duplicator’s dormant installers and four plugin flaws under exploitation

5 October · Plugins

Six plugin vulnerabilities to act on this week

Ordered by what to do first. Patchstack’s database marks three of the six as exploited. None is on CISA’s KEV list and we found no independent report of attacks, so treat that label as a warning rather than a confirmed campaign.

Figure 1 · At a glance

Four weeks of plugin flaws: what was flagged as exploited, and when.

QuestionAnswer
5 OctoberSix to act on; three flagged exploited by Patchstack
12 OctoberEight critical flaws, all exploitable without a login
19 OctoberFour under exploitation; LearnPress and WP Booking System to patch
26 OctoberDuplicator’s dormant installers and four flaws under exploitation
Separate advisoriesRank Math SEO PRO 3.0.123; Ninja Forms and WPC Product Bundles
The points that decide what to do about the WordPress plugin flaws covered in the October 2026 briefings, as stated in the sections below.
SeverityPlugin and CVEVulnerableFix
Critical, 9.8–10 · flagged exploitedRequest a Quote for WooCommerce (Addify) — CVE-2026-18143≤ 2.9.2Update to 2.9.3, released 26 September
Critical, 9.8 · flagged exploitedVisual Composer Website Builder — CVE-2026-12227≤ 45.16.0Update to 45.16.1 or later
Critical, 9.8DevKit Pro (DPlugins) — CVE-2026-14378≤ 2.3.0Update to the current 3.0 release
Critical, 9.3WordPress File Upload (Iptanus) — CVE-2026-62071≤ 5.1.10Update to 5.2.0 or later
High, 8.8 · flagged exploitedElementor — CVE-2026-620624.3.0–4.3.1Update to 4.3.2 or later
High, 7.4WP User Frontend — CVE-2026-758233.5.29–4.3.11Update to 4.3.12 or later

5 October · Plugins · detail

What each plugin flaw means, and the one to deal with first

Request a Quote for WooCommerce is the one to deal with first. It is Addify’s paid extension, sold on WooCommerce.com rather than listed in the wordpress.org directory, so its updates arrive through a WooCommerce.com subscription. Versions up to 2.9.2 let anyone, without logging in, upload an arbitrary file — on a PHP site, that means a webshell — when a public quote rule uses the multi-page popup flow. Patchstack rates it 10, Wordfence 9.8. Addify fixed it in 2.9.3 on 26 September, but Patchstack’s entry still said “no official patch available” on 5 October, so anyone going by that entry alone may have removed the plugin or be holding off. Update to 2.9.3; if a site cannot be updated today, deactivate the plugin until it can. Either way, check the quote upload folders and wp-content/uploads for PHP files that should not be there.

Two more of the six need no login at all. Visual Composer Website Builder up to 45.16.0 has a local file inclusion through its vcv-template parameter — the same class of bug as this week’s Core flaw — which can lead to code execution where an attacker can get a suitable file onto the server. It was fixed quietly in 45.16.1 in July and only disclosed on 23 September, so sites that update regularly are already covered. DevKit Pro up to 2.3.0 trusts an original_user_id cookie in a way that lets an anonymous visitor take over an administrator account. Patchstack names 2.3.1 as the fix, but the vendor’s changelog jumps from 2.2.3 to 3.0.0 with no security note, so update to the current 3.0 release rather than looking for a 2.3.1.

The WordPress File Upload flaw is a SQL injection that needs no login and lets an attacker read or change the database — password hashes, user roles, and any secrets plugins keep in wp_options. WP User Frontend’s flaw needs no login either, but only applies where the PHP sodium extension is missing and a registration page is set up: an attacker can then register with a higher role. WPScan says that means a role such as Editor, not administrator; Patchstack’s entry speaks of administrator access. Either way, check who registered recently.

Elementor 4.3.0 and 4.3.1 are an unusual case. They skip WordPress’s REST API nonce check for any request whose address contains elementor/v1/events/ — and because that text can be appended to any REST URL, every REST route on the site loses its protection against cross-site request forgery. Nonces are what stop another website from making requests in a logged-in administrator’s name; with them gone, an administrator only has to click a plain link for the attacker to, for example, create a second administrator. The affected code sits behind a hidden setting that is on by default for sites that first installed Elementor at 3.32.0 or later. Version 4.3.2, released on 24 September, closes it.

12 October · Plugins

Eight critical plugin flaws, all exploitable without a login

The first seven were disclosed by Wordfence on 9 October and published as CVEs on 10 October. All eight scores are Wordfence’s, shown on NVD as the CNA score; NVD has not done its own analysis. None is on CISA’s KEV list and none has been reported exploited. Every one has a fixed release.

SeverityPlugin and CVEVulnerableFix
Critical, 9.8Advanced IP Blocker — CVE-2026-104732, authentication bypass in its 2FA login≤ 8.13.13Update to 8.13.16, which also closes a second 2FA bypass through XML-RPC
Critical, 9.8Extensions For CF7 (HT Plugins) — CVE-2026-94589, file upload through the signature field≤ 3.4.5Update to 3.4.6
Critical, 9.83D Product Configurator for WooCommerce (Expivi) — CVE-2026-103889, code execution through Dompdf≤ 2.16.2Update to 2.16.3
Critical, 9.8WPCOM Member — CVE-2026-104803, social-login authentication bypass≤ 1.7.27Update to 1.8.0 or later
Critical, 9.1Blocksy Companion — CVE-2026-107645, registration as a Dokan vendor≤ 2.1.58Update to 2.1.59
Critical, 9.1PPOM for WooCommerce (Themeisle) — CVE-2026-104801, file deletion outside the uploads folder≤ 34.0.10Update to 34.0.11
Critical, 9.1Avada Builder (ThemeFusion) — CVE-2026-97670, action hooks run from form fields≤ 7.16.1Update Avada to 7.16.2
Critical, 9.1 · public exploitForminator (WPMU DEV) — CVE-2026-92229, shortcode execution≤ 1.57.2Update to the current 1.58.0

12 October · Plugins · detail

What each plugin flaw means, and which ones to deal with first

Forminator comes first, because it is the only one of the eight with working exploit code in public. Versions up to 1.57.2 pass a current_url value from an anonymous request into WordPress’s shortcode parser, so anyone can make the site run any shortcode it has registered. The CVE record describes this as arbitrary shortcode execution, not code execution. What an attacker can do with it depends on the shortcodes that other installed plugins and the theme provide, which is why some reports describe it as a route to remote code execution when combined with other plugins. WPMU DEV removed the vulnerable call in 1.57.2.1 and 1.57.3, both released on 17 September; a proof of concept and mass scanner appeared on GitHub on 19 September. Forminator has more than 600,000 installs. Wordfence lists three more flaws in the same versions — two unauthenticated stored XSS rated 7.2 and a missing authorization check rated 5.3 — which the current release also closes.

Blocksy Companion has the largest install base of the October seven, more than 300,000 sites, but the narrowest exposure. Its account modal accepted a role parameter at registration without respecting Dokan’s vendor-registration setting. The flaw is therefore relevant on sites that run WooCommerce with the Dokan marketplace plugin, where it gives an attacker a vendor account, not an administrator one.

Advanced IP Blocker is a reminder that a security plugin is still code on the attack surface. Its 2FA login flow could be bypassed: an attacker who knows the user ID of an account with the plugin’s 2FA enabled could try 6-digit codes with no rate limit. The fix in 8.13.14 adds a first-step token and a lockout after five failures, and 8.13.16, released on 10 October, closes a second bypass through XML-RPC. The other October flaws reach code execution or account takeover more directly. In Extensions For CF7 and the Expivi 3D Product Configurator, an anonymous visitor could upload or run PHP. WPCOM Member did not validate the state parameter of its social-login callback. PPOM let visitors delete files outside the uploads folder, including wp-config.php, and deleting that file is a known route to taking over an installation by re-running the setup.

Avada is a premium theme, so its fix arrives through the theme’s own updater, not through WordPress.org. The flaw lets an anonymous visitor trigger arbitrary WordPress action hooks through a field placeholder in an Avada form notification, which is how the default setup works, and can be used to delete trashed content permanently or take the site down. The CVE record numbers the vulnerable Builder versions in the 7.x series used by the theme, so update Avada to 7.16.2, released on 30 September, and let it update its bundled plugins.

19 October · Exploited · four plugins

Four plugin flaws under exploitation, each a straight path to administrator or code execution

All four carry Patchstack’s “known to be exploited” label in its database and all four need no login. Fixed releases exist for each. None of the four was on CISA’s Known Exploited Vulnerabilities catalog at its 16 October update, so the exploitation evidence is Patchstack’s own telemetry.

The Grid is the most serious of the four on paper and the hardest to inventory. Patchstack published it on 14 October from a 2 September report by Rafie Muhammad, and the CVE record followed on 16 October with a CVSS of 10: network, no privileges, no interaction, and a scope change. The plugin is commercial, so it will not appear in WordPress.org update checks; look for the-grid in the plugins folder of every site and compare the version in its header with 2.8.2. The CodeCanyon changelog visible on 19 October still ends at 2.8.1, so confirm the fixed build with the vendor if the updater offers nothing.

The three takeovers share a shape: a parameter that an anonymous visitor controls ends up in a function that writes user data. In MailOptin the attack needs a WordPress user registration opt-in form published on the site; the form’s identifier is visible in the page source. In Theme My Login the CVE record says exploitation applies to multisite installs in certain configurations, and the 7.2.2 changelog describes the fix as stopping a lost-password request from overwriting an account’s password on multisite; a single-site install may not be reachable, but with exploitation under way and the fix a one-line changelog entry, update anyway. In My Calendar the plugin’s own /my-calendar/ page is public by default after activation, so a default install is exposed. Patchstack classifies the My Calendar flaw as PHP object injection; the CVE record, assigned by Wordfence, and the plugin’s changelog describe it as privilege escalation through reflected shortcode injection. The fix is the same either way.

Plugin and CVEVulnerableFixWhat an attacker gets
The Grid (Theme-one) — CVE-2026-94169, CVSS 10≤ 2.8.12.8.2Runs commands on the server from the internet. A premium plugin sold through CodeCanyon, so the fix arrives through the vendor, not WordPress.org
Theme My Login — CVE-2026-89079, CVSS 9.8≤ 7.2.17.2.2 (current: 7.3.1)Changes any user’s password through the lost-password flow. The CVE record scopes it to multisite installs in certain configurations
My Calendar (Joe Dolson) — CVE-2026-104798, CVSS 9.8≤ 3.8.73.8.8 (current: 3.8.9)A public mcs parameter is run through do_shortcode, and a nested shortcode attribute reaches call_user_func, which can rewrite the first administrator’s credentials
MailOptin — CVE-2026-109515, CVSS 9.8≤ 1.2.78.61.2.78.7A field-mapping parameter on the subscribe endpoint is passed to wp_insert_user without an allow list, so an attacker can set any user’s password, including an administrator’s

19 October · Plugins · patch this week

LearnPress and WP Booking System: not yet exploited, fixed this week

LearnPress, with more than 70,000 installs, is vulnerable up to 4.4.10 to an unauthenticated PHP object injection, CVE-2026-104736, scored 9.8 and published by Wordfence on 17 October from a Wordfence PRISM finding; Patchstack published it on 16 October and also marks it as exploited. The checkout-email parameter of the checkout AJAX action is passed through sanitize_text_field, which does not strip serialized object syntax, stored in the LearnPress session table, and later unserialized with no allowed_classes restriction. Object injection on its own does nothing; it needs a gadget chain in some other code on the site. The CVE record does not name one, and neither does Patchstack. That is a reason to update to 4.4.11, released on 16 October, before someone finds one, not a reason to wait. Exploit aggregators already list a public proof of concept.

WP Booking System, with more than 10,000 installs, is fixed in 2.1.0.4, released on 16 October. CVE-2026-109369 is a missing authorization check: a subscriber who has already been given edit rights on at least one booking form can overwrite the plugin’s own access-control list and grant themselves and any other user edit access to every form. Wordfence scores it 6.8, because of that precondition and the high attack complexity; Patchstack rates its priority high and expects it to be exploited. The changelog entry for 2.1.0.4 says only “Security improvements”.

26 October · Plugins · exploited and patched

Duplicator’s dormant installers, and four plugin flaws under exploitation

Patchstack marks the last four as known to be exploited. Duplicator is not marked exploited yet; Patchstack expects it to be, and the reason it gets the top row is that updating the plugin does not reach every copy of the vulnerable code.

Duplicator is the one to think about rather than just update. Wordfence assigned CVE-2026-82814 on 21 October from a finding by Alex Thomas and its Argus analysis: the plugin deserialises untrusted content from the database during a migration, and the content can be put there without logging in, for instance as a comment. The payload then waits. Nothing happens until an administrator builds a package and runs a migration, which is the user interaction in the CVSS vector, and at that point the installer that Duplicator bundled into the package does the deserialising. That installer is a copy of the code as it was when the package was built. Updating the plugin to 5.0.0 changes future packages; it changes nothing inside the packages already sitting in storage, which still carry the old installer and, if the payload was planted before the package was built, the payload too. A package built before the fix should be rebuilt before it is ever imported, and a site that imports old packages on a routine, staging refreshes for example, should treat every one of them that way.

The other four are straightforward to act on and hard to be sure about afterwards. Each gives an anonymous visitor an account or code execution, and each is being used. OttoKit’s fix shipped on 8 October with no security note in the changelog, eight days before Patchstack published, so a fleet that looked only for security releases missed it. The Events Calendar’s object injection was fixed on 10 September; what changed is the exploited marker, which means a site that was slow to update in September needs the look-behind now. miniOrange’s 5.5.8 changelog says security updates for phone-based login and Patchstack says 5.5.8 is still vulnerable; 5.6.0 is the version that closes it.

Plugin and CVEVulnerableFixWhat an attacker gets
Duplicator and Duplicator Pro — CVE-2026-82814, CVSS 8.8 (Patchstack: 9.8)≤ 1.5.17 · Pro ≤ 4.6.105.0.0 (current: 5.0.6)Unauthenticated PHP object injection: untrusted database content is deserialised during a migration. The CVE vector requires user interaction, which is the migration itself
OttoKit, formerly SureTriggers — CVE-2026-110372, CVSS 9.8≤ 1.1.401.1.41 (current: 1.1.42)Becomes an administrator. Patchstack lists the required privilege as none; its summary speaks of a low-privilege user. Reported on 11 October, published on 16 October, exploited
LearnPress — CVE-2026-104736, CVSS 9.8≤ 4.4.104.4.11Unauthenticated PHP object injection through the checkout email parameter, covered last week; Patchstack now marks it exploited
miniOrange OTP Login, Verification and SMS Notifications — CVE-2026-103895, CVSS 8.1≤ 5.5.85.6.0Unauthenticated authentication bypass: log in as another user without the password. Exploited. 5,000 installs, so small in number and total in effect
The Events Calendar — CVE-2026-78006, CVSS 9.8; CVE-2026-84740, CVSS 6.5≤ 6.17.4; 6.12.0 to 6.17.5.06.17.4.1; 6.17.5.1 (current: 6.18.2)Unauthenticated object injection to code execution, published 11 September and now marked exploited; and unauthenticated shortcode execution, also exploited. 600,000 installs

Common questions

Common questions about the October plugin flaws

We use Request a Quote for WooCommerce. What should we do?

Check the version. Addify fixed the unauthenticated file upload in 2.9.3 on 26 September, so update to that through your WooCommerce.com account; Patchstack’s database had not caught up on 5 October and still listed no fix. If you cannot update today, deactivate the plugin until you can. Then check the quote upload folders, wp-content/uploads, and the administrator list, because the flaw lets anyone place a file on the server without logging in.

Is the Forminator flaw a remote code execution?

Not on its own. It lets anyone make the site run any shortcode that is registered on it. Whether that leads further depends on which shortcodes other plugins and the theme provide. A public exploit has existed since 19 September, so update to the current release regardless.

Does Theme My Login’s flaw affect a single-site install?

The CVE record says exploitation applies to multisite installs in certain configurations, and the 7.2.2 changelog describes the fix in terms of multisite. Patchstack lists it as exploited without that qualifier. Update regardless; the cost is one plugin update and the alternative is guessing which configuration you are in.

Duplicator is updated to 5.0.0. Why rebuild old packages?

Because the installer that runs a migration travels inside the package, and it is a copy of the code from when the package was built. A package built with 1.5.17 or earlier carries the vulnerable installer whatever the destination site has installed, and if the payload was planted in the database before the package was built, it carries that too. Rebuilding with 5.0.0 replaces both.

Choose the response path

A plugin on this list was installed while it was vulnerable: choose the response path.

The server under the sites

Get every PHP branch, the namespace setting and the account boundaries checked and proven.

Best when several servers need the PHP packages verified by changelog, the logs from 17 October read, the CloudLinux mitigation assessed against what customers run, and WP Toolkit’s cross-account risk reviewed, with a written result per host.

One site, one worrying result

Get the finding classified and the site restored to a trusted state.

Best when an UpdraftCentral-connected site shows a plugin or administrator you did not create, a PHP worker wrote something it should not have, or an exploited plugin left an account behind, and you want every layer removed in one pass rather than one at a time.