Classic Addons – WPBakery Page Builder <= 3.0 - Inclusão Local Limitada de Arquivos PHP Autenticado (Contributor+)

An attacker exploiting this LFI vulnerability could gain significant control over a WordPress site. By leveraging the 'style' parameter, a contributor-level user (or higher, with administrator permissions) can include and execute arbitrary PHP code. This could lead to the disclosure of sensitive information stored on the server, such as database credentials or configuration files. Furthermore, the attacker could potentially execute malicious code, leading to complete compromise of the WordPress installation and potentially the underlying server. The ability to execute arbitrary code opens the door to a wide range of attacks, including defacement, data theft, and the installation of backdoors.

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. Reservado2024-11-28
2. Publicada2024-12-04
3. EPSS atualizado2026-04-02

The primary mitigation for CVE-2024-11952 is to upgrade the Classic Addons – WPBakery Page Builder plugin to a patched version. If upgrading immediately is not possible due to compatibility issues or testing requirements, consider temporarily restricting file upload permissions for users with Contributor access. Additionally, implement strict input validation on the 'style' parameter to prevent malicious file paths from being included. Web Application Firewalls (WAFs) configured to filter out suspicious file inclusion attempts can provide an additional layer of protection. Monitor WordPress logs for unusual file access patterns.

Instalações ativas

3KNicho

Avaliação do plugin