dbcve.org
Wpbakery Visual Composer Whmcs ElementsWordPress extension · Voidcoders

CVE-2024-10172

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-21
Fix available
A fix is available. Upgrade to 1.0.4.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The WPBakery Visual Composer WHMCS Elements plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's void_wbwhmcse_laouts_search shortcode in all versions up to, and including, 1.0.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WPBakery Visual Composer WHMCS Elements WordPress plugin versions up to 1.0.4 contains a stored XSS vulnerability in the void_wbwhmcse_laouts_search shortcode. Authenticated attackers with contributor-level permissions can inject malicious JavaScript via unsanitized user-supplied attributes in the shortcode, which executes when other users view the compromised pages.

MitigationUpdate the plugin to version 1.0.5 or later which includes proper input sanitization and output escaping. Until patched, review pages using this shortcode and consider restricting shortcode usage to trusted administrator-level users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wpbakery Visual Composer Whmcs ElementsWordPress extension
Affected:< 1.0.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > look for 'Voidcoders Wpbakery Visual Composer Whmcs Elements' and note the version number displayed there, or check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The version number is less than 1.0.4.1 (for example, 1.0.4, 1.0.3, etc.)
  2. Find pages using the vulnerable shortcode
    Search your WordPress database for the shortcode name 'void_wbwhmcse_laouts_search' in the wp_posts table, or use a plugin like 'Search Regex' to scan post content for this shortcode string
    Affected if Any posts or pages contain the [void_wbwhmcse_laouts_search] shortcode
  3. Inspect shortcode attributes for injected scripts
    Examine the content of pages containing the shortcode; look for any unexpected JavaScript, script tags, event handlers (onclick, onload, onerror), or suspicious URL patterns within the shortcode attributes
    Affected if The shortcode attributes contain unescaped HTML or JavaScript such as <script>, javascript:, or on* event handlers
  4. Check user roles for potential attackers
    Review your WordPress user list (Users > All Users) and verify that only trusted administrators have permission to create or edit content containing this shortcode; contributor-level users should not have this access if unpatched
    Affected if Contributor-level or author-level users have the ability to create or edit pages containing this shortcode

You are affected if the plugin version is below 1.0.4.1 AND pages containing the void_wbwhmcse_laouts_search shortcode exist with unescaped HTML or JavaScript in their attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.4.1 or later
Fixed in 1.0.4.1
Interim mitigation

Update the plugin to version 1.0.5 or later which includes proper input sanitization and output escaping. Until patched, review pages using this shortcode and consider restricting shortcode usage to trusted administrator-level users only.

Recommended fix High confidence

1.0.4.1

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'WPBakery Visual Composer WHMCS Elements' plugin
  4. Click 'Update now' if an update is available, or manually upload version 1.0.4.1 from the WordPress plugin repository
  5. Verify the update was successful by confirming the plugin version is 1.0.4.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpbakery Visual Composer Whmcs Elements Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10172 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data