Security alert · High
WordPress plugin vulnerabilities: 5 plugins including Optimole with 200,000 installs
· 3 minutes read · Centoculus Security Team
Known since
Affected: WordPress plugins: Kanbanz by Softaculous, FooBox, Multi Step for Contact Form 7, MembershipWorks, Optimole
Vulnerabilities have been disclosed in five WordPress plugins. The most serious is a broken access control flaw in Kanbanz by Softaculous with a CVSS score of 8.1. The most widely used affected plugin is Optimole, with around 200,000 active installations. None of the vulnerabilities is reported as actively exploited.
Kanbanz by Softaculous (3,000 active installations)
Versions before 1.0.3 contain a broken access control vulnerability in several admin-ajax handlers. Authenticated users with the Kanban Staff role can read and modify boards they are not members of, including task data, subtasks, labels, comments and attachments. The issue is tracked as CVE-2026-127215 with a CVSS score of 8.1. Update to version 1.0.3 or later.
FooBox – Lightbox & Modal Popup (100,000 active installations)
All versions up to and including 2.8.7 are vulnerable to stored DOM-based cross-site scripting via the img alt attribute inside a .wp-caption container. On a default installation, exploitation requires contributor-level access; when bbPress 2.6.20 is installed with a public forum and suitable moderation settings, subscriber-level users can exploit it. The issue is tracked as CVE-2026-120687 with a CVSS score of 7.2. Update to the latest version.
Multi Step for Contact Form 7 (10,000 active installations)
All versions up to and including 2.9.1 are vulnerable to stored cross-site scripting that unauthenticated attackers can exploit. Exploitation requires the form option 'Save every step' and the Database for Contact Form 7 companion plugin with its 'Expandable' table option, both disabled by default. The issue is tracked as CVE-2026-116753 with a CVSS score of 7.2. Update to the latest version.
MembershipWorks – Membership, Events & Directory (2,000 active installations)
All versions up to and including 6.17 are vulnerable to stored cross-site scripting because member-supplied data from the MembershipWorks API, such as member names and event titles, is output without escaping. Unauthenticated attackers can inject scripts that run when users view the affected pages. The issue is tracked as CVE-2026-119643 with a CVSS score of 7.2. Update to the latest version.
Optimole (200,000 active installations)
All versions up to and including 4.2.19 are vulnerable to arbitrary file deletion due to insufficient file path validation, which can lead to remote code execution if a file such as wp-config.php is deleted. Unauthenticated attackers can stage a payload in a comment, but exploitation also requires PEAR's Archive_Tar library on the host and an administrator using the plugin's Rename control on an attachment. The issue is tracked as CVE-2026-124969 with a CVSS score of 7.1. Update to the latest version.
How to check your sites
In the WordPress dashboard, open the Plugins page and check whether any of the plugins above are installed and which version they run. With WP-CLI, run wp plugin list to see installed plugins, their versions and available updates, and update them with wp plugin update <plugin-slug>. If no update is available for a plugin you use, deactivate and remove it until a fixed version is released.
Sources
More sources (8)
- https://nvd.nist.gov/vuln/detail/CVE-2026-120687
- https://nvd.nist.gov/vuln/detail/CVE-2026-124969
- https://nvd.nist.gov/vuln/detail/CVE-2026-127215
- https://wordpress.org/plugins/cf7-multi-step/
- https://wordpress.org/plugins/memberfindme/
- https://wordpress.org/plugins/foobox-image-lightbox/
- https://wordpress.org/plugins/optimole-wp/
- https://wordpress.org/plugins/kanbanz/
More on WordPress
- WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
- WordPress plugin vulnerabilities: 11 plugins, including Shortcodes for Phlox theme
- WordPress plugin vulnerabilities: 10 plugins including UpdraftPlus
- WordPress plugin vulnerabilities: 7 plugins, including Custom Twitter Feeds
- WordPress plugin vulnerabilities: 7 plugins including NextGEN Gallery
- WordPress plugin vulnerabilities: 12 plugins including WS Form LITE
- WordPress plugin vulnerabilities: 13 plugins including TranslatePress
- WordPress plugin vulnerabilities: 6 plugins including User Frontend
- WordPress plugin vulnerabilities: 5 plugins, including LiteSpeed Cache
- WordPress plugin vulnerabilities: 6 plugins affected, including SureCart
If you run CMS or shop systems, also check
- Drupal core: critical installer flaw can allow site takeover without login
- WordPress core race condition lets attackers run code during upgrades, actively exploited
- WordPress update fixes code injection flaw, exploitation attempts observed
- Drupal Commerce Core authorization bypass actively exploited (CVE-2026-118539)
- WordPress plugin vulnerabilities: 19 plugins including W3 Total Cache
- WordPress plugin vulnerabilities: 10 plugins, including Welcart e-Commerce
- Magento stores hit by evasive JavaScript loader hidden in CMS blocks
- CryptoPayment Gateway WordPress plugin flaw CVE-2026-81648 now actively exploited
- Adobe Commerce and Magento: exploited file upload flaw allows code execution
Related posts
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.
Alerts ·
PHP fixes critical session flaw CVE-2026-115560 and six other code execution bugs
PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13 fix CVE-2026-115560 (CVSS 9.2), a session serializer mismatch that can lead to code execution. The same release fixes six more critical flaws, so every PHP server should be updated.
Alerts ·
Ruby: seven memory-safety flaws in regex and string handling, remote code execution possible
Ruby 4.0.10, 3.4.13 and 3.3.14 fix seven memory-safety flaws in the regex engine and in string case conversion. For five of them, the maintainers know of proofs of concept that run code. Ruby 3.2 and older get no fix.