CVE-2024-10172: The WPBakery Visual Composer WHMCS Elements plugin for WordPress is vulnerable to Stored Cross-Site Scripting

Q: How do I fix CVE-2024-10172?

wpbakery visual composer whmcs elements: upgrade to 1.0.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-10172 being exploited?

CVE-2024-10172 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-10172 affect?

CVE-2024-10172 affects wpbakery visual composer whmcs elements. Severity is medium (CVSS 6.4). 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 sanit

Q: How urgent is CVE-2024-10172?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 6.4UPGRADE

CVE-2024-10172 is a medium-severity flaw (CVSS 6.4) affecting wpbakery visual composer whmcs elements. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 w

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-11-21
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: voidcoders

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-11-21 11:15 UTCPublished CVE record published
2026-06-17 06:55 UTCUpdated Record last modified

voidcoders wpbakery visual composer whmcs elements UPGRADE

Affected: < 1.0.4.1

Fixed in: 1.0.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wpbakery-visual-composer-whmcs-elements || rpm -q wpbakery-visual-composer-whmcs-elements || wpbakery-visual-composer-whmcs-elements --version

2. UPGRADE to 1.0.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wpbakery-visual-composer-whmcs-elements

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wpbakery-visual-composer-whmcs-elements

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-10172?

wpbakery visual composer whmcs elements: upgrade to 1.0.4.1. Exact commands for each OS are on this page.

Is CVE-2024-10172 being exploited?

CVE-2024-10172 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-10172 affect?

CVE-2024-10172 affects wpbakery visual composer whmcs elements. Severity is medium (CVSS 6.4). 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 sanit

How urgent is CVE-2024-10172?

Priority 33/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs