high CVSS 8.8

CVE-2024-3499·PHP vulnerability

The ElementsKit Elementor addons plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.1.0 via the generate_navigation_markup function of the Onepage Scroll module. This makes it possible for authenticated attackers, with contributor-level access and above, 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
3.1.1
Published
2024-05-02

Affected versions

Until: 3.1.1

Fixed in: 3.1.1

How to fix this CVE

WordPress administrators using the ElementsKit Elementor addons plugin must immediately upgrade to version 3.1.1 or later to patch the Local File Inclusion vulnerability in the Onepage Scroll module. This vulnerability allows authenticated contributors and above to include arbitrary files and execute PHP code on the server. Update the plugin through the WordPress admin dashboard or via command line to eliminate the attack vector.

sudo dnf update php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET.*generate_navigation_markup.*\.\.[\/\\]|file_path=[\/\\].*\.(php|phtml|php3|php4|php5|pht)

WAF mitigation (if patching is not yet possible)

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

Block HTTP requests containing 'generate_navigation_markup' parameter combined with directory traversal sequences (../ or ..\ ) or suspicious file path parameters pointing to web-accessible directories. Implement input validation rules to reject path traversal attempts in the Onepage Scroll module endpoints.

How to check if you are affected

  1. Step 1: Check installed PHP version with `php -v` and verify it is the latest stable release for your distribution.
  2. Step 2: List active WordPress plugins with `wp plugin list --allow-root` and confirm ElementsKit version is 3.1.1 or higher.
  3. Step 3: Search web server access logs for requests containing 'generate_navigation_markup' parameter or file path traversal patterns: `grep -i 'generate_navigation_markup\|\.\./' /var/log/apache2/access.log | head -20`
  4. Step 4: Verify the plugin update was successful by checking the plugin version in WordPress admin > Plugins, or via `wp plugin get elementskit-lite --field=version --allow-root`

FAQ

What is CVE-2024-3499?

CVE-2024-3499 is a Local File Inclusion (LFI) vulnerability in the ElementsKit Elementor addons plugin for WordPress that allows authenticated users with contributor-level permissions or higher to include and execute arbitrary PHP files stored on the server, potentially leading to unauthorized code execution.

Is CVE-2024-3499 being actively exploited?

No, CVE-2024-3499 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been disclosed, though the vulnerability requires only contributor-level WordPress access to trigger.

What versions of ElementsKit are affected by CVE-2024-3499?

All versions of ElementsKit Elementor addons up to and including version 3.1.0 are vulnerable; version 3.1.1 and later contain the fix.

How do I check if my WordPress site is vulnerable to CVE-2024-3499?

Access your WordPress admin dashboard, navigate to Plugins, and check the ElementsKit version number. If it shows 3.1.0 or earlier, your site is vulnerable and requires immediate update.

Does Defensia detect CVE-2024-3499?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If WordPress and ElementsKit plugins are monitored on your servers, CVE-2024-3499 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-3499. Free for 1 server.

Get started free