high CVSS 8.8

CVE-2024-5709·PHP vulnerability

The WPBakery Visual Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 7.7 via the 'layout_name' parameter. This makes it possible for authenticated attackers, with Author-level access and above, and with post permissions granted by an Administrator, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Severity
high
Software
PHP
Fixed in
7.8
Published
2024-08-06

Affected versions

Until: 7.8

Fixed in: 7.8

How to fix this CVE

Update WPBakery Visual Composer to version 7.8 or later, which addresses the local file inclusion vulnerability in the layout_name parameter. This plugin flaw allows authenticated WordPress users with Author-level permissions to execute arbitrary PHP code by manipulating file inclusion logic. Immediately patch all WordPress installations running WPBakery 7.7 and earlier, especially those with untrusted content editors or guest authors.

sudo dnf update php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET.*layout_name=[^\s&]*(\.\.\/|%2e%2e%2f|php://|file://)

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Block requests to WordPress admin-ajax.php or vc_* endpoints containing the 'layout_name' parameter with path traversal sequences (../, %2e%2e%2f) or PHP stream wrappers (php://, file://). Implement a strict allowlist of valid layout_name values if possible.

How to check if you are affected

  1. Step 1: Check WPBakery version by logging into WordPress admin panel and navigating to Plugins → Installed Plugins, then locate WPBakery Visual Composer and verify the version number is 7.8 or higher
  2. Step 2: Query the WordPress database directly: mysql -u wordpress_user -p wordpress_db -e "SELECT option_value FROM wp_options WHERE option_name='wpbakery_plugin_version';" to confirm installed version
  3. Step 3: Search WordPress access logs for POST/GET requests containing 'layout_name' parameter: grep -E 'layout_name|vc_' /var/log/apache2/access.log | head -50
  4. Step 4: After updating, verify the new version by re-checking wp_options table or the Plugins dashboard to confirm version 7.8 or higher is active

FAQ

What is CVE-2024-5709?

CVE-2024-5709 is a local file inclusion vulnerability in WPBakery Visual Composer affecting versions up to 7.7, where the layout_name parameter fails to properly validate user input, allowing authenticated WordPress editors to include and execute arbitrary PHP files from the server.

Is CVE-2024-5709 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploit code has been released. However, the risk remains high for sites with untrusted editor-level users.

What versions of PHP are affected by CVE-2024-5709?

This vulnerability affects WPBakery Visual Composer for WordPress in all versions from the earliest available up to and including version 7.7. PHP itself is not directly vulnerable; rather, the WPBakery plugin running on PHP-based WordPress sites is affected.

How do I check if my server is vulnerable to CVE-2024-5709?

Log into your WordPress admin dashboard, go to Plugins, and find WPBakery Visual Composer. If the version is 7.7 or lower, your site is vulnerable. Alternatively, use WP-CLI: wp plugin get wpbakery --field=version

Does Defensia detect CVE-2024-5709?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If WPBakery Visual Composer is installed on a monitored WordPress server, CVE-2024-5709 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2026-39337CVSS 10ChurchCRM is an open-source church management system. Prior to 7.1.0, critical pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The "$dbPassword" variable is not sanitized. This vulnerability exists due to an incomplete fix for CVE-2025-62521. This vulnerability is fixed in 7.1.0.
CVE-2024-5932CVSS 10The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files.
CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.
CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.
CVE-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-5709. Free for 1 server.

Get started free