Skip to main content
Vulnerability Database/CVE-2025-47659

CVE-2025-47659: WPBakery Visual Composer WHMCS XSS Flaw

CVE-2025-47659 is a stored XSS vulnerability in WPBakery Visual Composer WHMCS Elements plugin that enables attackers to inject malicious scripts. This article covers the technical details, affected versions up to 1.0.4.3, and steps to secure your site.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-47659 Overview

CVE-2025-47659 is a stored Cross-Site Scripting (XSS) vulnerability in the voidcoders WPBakery Visual Composer WHMCS Elements plugin for WordPress (void-visual-whmcs-element). The flaw stems from improper neutralization of user input during web page generation [CWE-79]. All plugin versions up to and including 1.0.4.3 are affected. An authenticated attacker with contributor-level or higher privileges can inject malicious JavaScript that executes in the browsers of users who view the affected pages. The vulnerability requires user interaction and crosses a security scope boundary, enabling attackers to hijack sessions, steal credentials, or redirect visitors to malicious destinations.

Critical Impact

Authenticated attackers can inject persistent JavaScript payloads into WordPress pages, enabling session hijacking and credential theft against site administrators and visitors.

Affected Products

  • WPBakery Visual Composer WHMCS Elements (void-visual-whmcs-element) plugin for WordPress
  • All versions from unspecified initial release through 1.0.4.3
  • WordPress sites using the voidcoders WHMCS integration shortcodes

Discovery Timeline

  • 2025-05-07 - CVE-2025-47659 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-47659

Vulnerability Analysis

The vulnerability is a stored XSS flaw in the WPBakery Visual Composer WHMCS Elements plugin. The plugin extends WPBakery Page Builder with shortcodes for integrating WHMCS billing content into WordPress pages. User-supplied attributes passed to these shortcodes are rendered into the page markup without adequate sanitization or output encoding.

Because the payload is persisted in the WordPress database, it executes every time a visitor loads the affected page. The attack crosses a scope boundary because content authored by a lower-privileged contributor can execute in the context of administrators or anonymous visitors viewing the site frontend.

Root Cause

The root cause is improper neutralization of input during web page generation. Shortcode handlers in the plugin accept attribute values and emit them into HTML without escaping functions such as esc_attr(), esc_html(), or wp_kses(). Any attacker able to author or edit a post containing the vulnerable shortcode can embed arbitrary HTML and JavaScript that WordPress serves back to visitors.

Attack Vector

Exploitation requires network access to the WordPress site and an authenticated account with post-editing privileges. The attacker inserts a crafted shortcode attribute containing JavaScript into a page or post. When a logged-in administrator or site visitor renders the page, the injected script executes in their browser session, inheriting the origin of the WordPress site.

Typical post-exploitation actions include stealing authentication cookies, performing actions as the targeted user through forged requests, injecting cryptominers or redirects, and pivoting toward full site takeover if an administrator is targeted. See the Patchstack Vulnerability Report for additional technical context.

Detection Methods for CVE-2025-47659

Indicators of Compromise

  • Unexpected <script> tags, event handlers (onerror, onload, onmouseover), or javascript: URIs stored within WordPress wp_posts content.
  • Shortcode attributes for void-visual-whmcs-element containing encoded HTML entities, inline JavaScript, or references to external domains.
  • Outbound browser requests from site visitors to attacker-controlled domains originating from pages that render WHMCS Elements shortcodes.

Detection Strategies

  • Query the WordPress database for suspicious patterns in posts containing voidcoders shortcodes, including <script, onerror=, and document.cookie.
  • Review web server access logs for POST requests to /wp-admin/post.php from contributor-level accounts followed by anomalous frontend traffic.
  • Deploy Content Security Policy (CSP) reporting to surface inline script violations on pages that embed WHMCS content.

Monitoring Recommendations

  • Alert on new or modified WordPress posts that include the vulnerable shortcode along with HTML event attributes or script tags.
  • Monitor administrator session activity for anomalous actions following page views, such as plugin installations or new user creation.
  • Track plugin inventory to identify WordPress instances still running void-visual-whmcs-element version 1.0.4.3 or earlier.

How to Mitigate CVE-2025-47659

Immediate Actions Required

  • Audit all WordPress sites for the presence of the void-visual-whmcs-element plugin and record installed versions.
  • Review existing posts and pages for malicious shortcode content and remove any unauthorized scripts.
  • Restrict post-editing privileges to trusted accounts and enforce multi-factor authentication for all contributors and administrators.

Patch Information

At the time of publication, the vendor advisory tracked by Patchstack indicates the vulnerability affects all versions through 1.0.4.3. Administrators should consult the Patchstack Vulnerability Report for the current fixed version and apply updates through the WordPress plugin management interface.

Workarounds

  • Deactivate and remove the void-visual-whmcs-element plugin until a patched version is confirmed deployed.
  • Deploy a Web Application Firewall (WAF) rule that blocks shortcode attributes containing <script, javascript:, or HTML event handlers.
  • Enforce a strict Content Security Policy that disallows inline scripts (script-src 'self') on all public-facing WordPress pages.
bash
# Example WP-CLI commands to inventory and disable the vulnerable plugin
wp plugin list --name=void-visual-whmcs-element --fields=name,status,version
wp plugin deactivate void-visual-whmcs-element
wp plugin delete void-visual-whmcs-element

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.