high CVSS 8.8

CVE-2024-3813·PHP vulnerability

The tagDiv Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.8 via the 'td_block_title' shortcode 'block_template_id' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, 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 php file type can be uploaded and included.

Severity
high
Software
PHP
Fixed in
4.9
Published
2024-06-15

Affected versions

Until: 4.9

Fixed in: 4.9

How to fix this CVE

WordPress sites using the tagDiv Composer plugin must upgrade to version 4.9 or later to patch a local file inclusion vulnerability that allows authenticated contributors to execute arbitrary PHP code. Review your WordPress plugins immediately and apply the security update through the WordPress admin dashboard or via command line tools. Additionally, audit user permissions and restrict contributor-level access to trusted personnel only.

sudo dnf check-update && sudo dnf upgrade php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST requests to wp-admin/admin-ajax.php with shortcode parameters containing 'td_block_title' and 'block_template_id' attributes pointing to files outside the expected template directory (e.g., ../../../../etc/passwd or paths containing ../ sequences)

WAF mitigation (if patching is not yet possible)

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

Block or rate-limit POST requests to wp-admin/admin-ajax.php that contain the 'td_block_title' shortcode with 'block_template_id' parameters including path traversal sequences (../, ..\ ) or absolute paths. Implement strict input validation to allow only alphanumeric characters and underscores in the block_template_id parameter.

How to check if you are affected

  1. Step 1: Check installed PHP version with: php -v
  2. Step 2: Verify tagDiv Composer plugin version in WordPress by navigating to Plugins > Installed Plugins and locating 'tagDiv Composer' — note the version number displayed
  3. Step 3: Search WordPress error logs at wp-content/debug.log for patterns like 'td_block_title', 'block_template_id', or file inclusion attempts with unusual file paths
  4. Step 4: After updating to version 4.9+, re-run the WordPress admin plugin check to confirm the new version is active and no older files remain in the plugins directory

FAQ

What is CVE-2024-3813?

CVE-2024-3813 is a local file inclusion flaw in the tagDiv Composer WordPress plugin that permits authenticated contributors to include and execute arbitrary PHP files on the server, bypassing access controls and enabling remote code execution.

Is CVE-2024-3813 being actively exploited?

No, CVE-2024-3813 is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available, though the vulnerability is trivial to weaponize.

What versions of the tagDiv Composer plugin are affected by CVE-2024-3813?

All versions of tagDiv Composer up to and including version 4.8 are vulnerable; version 4.9 and later include the security fix.

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

Log into your WordPress admin panel, navigate to Plugins > Installed Plugins, find 'tagDiv Composer', and confirm the version is 4.8 or lower. If so, your site requires an immediate update.

Does Defensia detect CVE-2024-3813?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the tagDiv Composer plugin is active on a monitored WordPress site, CVE-2024-3813 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-3813. Free for 1 server.

Get started free