high CVSS 8.8

CVE-2024-3564·PHP vulnerability

The Content Blocks (Custom Post Widget) plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.3.0 via the plugin's 'content_block' shortcode. 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.3.1
Published
2024-06-01

Affected versions

Until: 3.3.1

Fixed in: 3.3.1

How to fix this CVE

Update PHP to the latest stable version available in your distribution's repository to patch CVE-2024-3564. If you are running the Content Blocks (Custom Post Widget) WordPress plugin, ensure it is upgraded to version 3.3.1 or later. This vulnerability allows authenticated contributors to execute arbitrary PHP code through malicious file inclusion, requiring immediate patching on production systems.

sudo dnf update php

Defensia detects this vulnerability

WAF mitigation (if patching is not yet possible)

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

Implement a WAF rule to block HTTP requests containing the parameter or attribute pattern [content_block] in POST or GET parameters, especially those originating from user accounts with contributor or editor roles. Additionally, block requests attempting to include file paths with directory traversal sequences (../ or ..\) within shortcode attributes.

How to check if you are affected

  1. Run `php -v` to check your current PHP version and compare it against the latest available version in your distribution's repository
  2. If using WordPress, navigate to Plugins → Installed Plugins and verify the Content Blocks (Custom Post Widget) plugin version is 3.3.1 or later; if not present, the vulnerability does not apply
  3. Search your web server logs (typically /var/log/apache2/access.log or /var/log/nginx/access.log) for patterns containing 'content_block' shortcode requests from contributor-level user accounts
  4. After patching, run `php -v` again and confirm the version number has increased; restart Apache or Nginx with `sudo systemctl restart apache2` or `sudo systemctl restart nginx`

FAQ

What is CVE-2024-3564?

CVE-2024-3564 is a local file inclusion vulnerability in the Content Blocks (Custom Post Widget) WordPress plugin that allows authenticated contributors to manipulate the content_block shortcode to load and execute arbitrary PHP files from the server, bypassing access controls and enabling remote code execution.

Is CVE-2024-3564 being actively exploited?

No, CVE-2024-3564 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available, though the vulnerability's ease of exploitation makes proactive patching critical.

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

This vulnerability affects the Content Blocks (Custom Post Widget) WordPress plugin in all versions up to and including 3.3.0; it is patched in version 3.3.1 and later. PHP itself is not vulnerable—the issue is plugin-specific.

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

If running WordPress, use `wp plugin list --field=name,version` (via WP-CLI) to check the Content Blocks plugin version; if it is 3.3.0 or earlier, your server is vulnerable. Alternatively, manually check the plugin folder at /wp-content/plugins/custom-post-widget/ and review the plugin header comment in the main file.

Does Defensia detect CVE-2024-3564?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP or the Content Blocks plugin is installed on a monitored server, CVE-2024-3564 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-3564. Free for 1 server.

Get started free