Classic Addons – WPBakery Page Builder <= 3.0 - Authenticated (Contributor+) Begrenzte Lokale PHP-Datei-Inklusion

An attacker exploiting this vulnerability could achieve remote code execution on the WordPress server. By leveraging the 'style' parameter, an authenticated contributor can include and execute arbitrary PHP code. This could lead to the theft of sensitive data, modification of website content, or even complete server compromise. The ability to upload images or other file types that can be included amplifies the attack surface, allowing attackers to inject malicious PHP code into seemingly harmless files. This vulnerability shares similarities with other LFI exploits where file inclusion is used to bypass access controls and execute arbitrary code.

WordPress websites utilizing the Classic Addons – WPBakery Page Builder plugin, particularly those with multiple users granted Contributor-level access or higher, are at risk. Shared hosting environments where users have limited control over plugin updates and configurations are also particularly vulnerable. Sites with legacy configurations or outdated security practices are more susceptible to exploitation.

• wordpress: Use wp-cli to check the installed plugin version:

wp plugin list | grep 'Classic Addons'

• wordpress: Search plugin files for the vulnerable 'style' parameter usage. Look for patterns like include($_GET['style']); or similar. • generic web: Monitor web server access logs for requests containing suspicious file paths in the 'style' parameter, such as /../../../../etc/passwd. • generic web: Check WordPress error logs for PHP inclusion errors related to the 'style' parameter.

1. 2024-12-04Disclosure

   disclosure

1. Reserviert2024-11-28
2. Veröffentlicht2024-12-04
3. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2024-11952 is to immediately update the Classic Addons – WPBakery Page Builder plugin to a version that addresses the vulnerability. If an immediate upgrade is not feasible due to compatibility issues or breaking changes, consider restricting file upload permissions for users with Contributor access. Implement strict input validation on the 'style' parameter to prevent malicious file paths. Web Application Firewalls (WAFs) configured to detect and block attempts to include arbitrary files can provide an additional layer of defense. Monitor WordPress access logs for suspicious file inclusion attempts.

Aktive Installationen

3KNische

Plugin-Bewertung