wpbakery vulnerabilities
Recent CVEs affecting wpbakery products. 8 tracked.
wpbakery has 8 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 8. Most recent: 2025-10-18. Highest priority: CVE-2024-5709 (score 47/100).
- CVE-2025-10006 MEDIUM 6.4 UPGRADE The WPBakery Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's '
- CVE-2025-11160 MEDIUM 6.4 UPGRADE The WPBakery Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Custom JS
- CVE-2025-11161 MEDIUM 6.4 UPGRADE The WPBakery Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the vc_custom_
- CVE-2025-7502 MEDIUM 6.4 UPGRADE The WPBakery Page Builder for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via
- CVE-2025-4968 MEDIUM 6.4 UPGRADE The WPBakery Page Builder for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via
- CVE-2024-5709 HIGH 8.8 UPGRADE The WPBakery Visual Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to,
- CVE-2024-5708 MEDIUM 6.4 UPGRADE The WPBakery Visual Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘link’
- CVE-2024-43953 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in webcodin
FAQ
How do I fix wpbakery vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is wpbakery being exploited right now?
None of the tracked wpbakery CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which wpbakery CVE should I patch first?
CVE-2024-5709 currently ranks highest (47/100): The WPBakery Visual Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to,.