Innovs WPBakery Visual Composer WHMCS Elements
void-visual-whmcs-element · plugin
Known security vulnerabilities for Innovs WPBakery Visual Composer WHMCS Elements. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
2 with no official fix seen · latest Dec 24, 2025
Before you install
Do not install
- 2 records show no fix in the latest wordpress.org release.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.0.4.3 · last updated Dec 2, 2025 · 1K+ installs
wordpress.org status checked on Nov 20, 2026
Vulnerabilities
- Medium 6.5
CVE-2025-47659login requiredno fix seen
WordPress WPBakery Visual Composer WHMCS Elements plugin <= 1.0.4.3 - Cross Site Scripting (XSS) vulnerability
- Medium 5.9
CVE-2025-68574high privilegeno fix seen
WordPress WPBakery Visual Composer WHMCS Elements plugin <= 1.0.4.3 - Cross Site Scripting (XSS) vulnerability
- Medium 5.4
CVE-2024-10172contributor+≤ 1.0.4
WPBakery Visual Composer WHMCS Elements <= 1.0.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via void_wbwhmcse_laouts_search Shortcode
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (1.0.4.3) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.