CVE-2024-10172: WPBakery Visual Composer WHMCS Elements <= 1.0.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via void_wbwhmcse_laouts_search Shortcode
The WPBakery Visual Composer WHMCS Elements plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's voidwbwhmcselaoutssearch 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-10172?
CVE-2024-10172 is classified as a high severity vulnerability due to the potential for Stored Cross-Site Scripting attacks.
How do I fix CVE-2024-10172?
To fix CVE-2024-10172, you should update the WPBakery Visual Composer WHMCS Elements plugin to version 1.0.5 or later.
Who is affected by CVE-2024-10172?
CVE-2024-10172 affects all versions of the WPBakery Visual Composer WHMCS Elements plugin up to and including 1.0.4.
What types of attacks can CVE-2024-10172 facilitate?
CVE-2024-10172 can facilitate Stored Cross-Site Scripting (XSS) attacks by allowing malicious scripts to be stored and executed in user sessions.
What are the key components of CVE-2024-10172?
The key components of CVE-2024-10172 include insufficient input sanitization and output escaping in the void_wbwhmcse_laouts_search shortcode.