critical CVSS 9.1

CVE-2024-5450·PHP vulnerability

The Bug Library WordPress plugin before 2.1.1 does not check the file type on user-submitted bug reports, allowing an unauthenticated user to upload PHP files

Severity
critical
Software
PHP
Fixed in
2.1.1
Published
2024-07-13

Affected versions

Until: 2.1.1

Fixed in: 2.1.1

How to fix this CVE

Update the Bug Library WordPress plugin to version 2.1.1 or later, which implements proper file type validation on user-submitted bug reports. This prevents unauthenticated attackers from uploading executable PHP files to your server. If you cannot update immediately, disable the bug report upload feature or restrict access to authenticated users only.

sudo dnf check-update php && sudo dnf update php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST requests to wp-content/plugins/bug-library/upload.php (or similar) containing PHP MIME types or .php file extensions in the filename parameter; alternatively, detecting recently uploaded .php files in the plugin's upload directory with creation timestamps matching access log entries

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 sanitize POST requests to bug report submission endpoints that contain PHP file extensions (.php, .php3, .php4, .php5, .phtml, .phar) in the 'file' or 'attachment' parameter; implement MIME type validation on the server side to reject application/x-php and similar executable MIME types

How to check if you are affected

  1. Check installed PHP version: php -v
  2. Verify Bug Library plugin version in WordPress admin: Settings > Plugins > Bug Library (note the version number)
  3. Search web server logs for suspicious file uploads: grep -i '\.php' /var/log/apache2/access.log | grep -i 'upload\|bug-report'
  4. Confirm the plugin has been updated to 2.1.1+: wp plugin list --allow-root | grep 'bug-library' (if using WP-CLI)

Indicators of compromise

  • Uploaded .php files in wp-content/plugins/bug-library/uploads/ directory
  • HTTP POST requests with Content-Disposition headers containing .php extensions
  • Suspicious PHP execution from the bug report upload directory in access logs

FAQ

What is CVE-2024-5450?

This vulnerability in the Bug Library WordPress plugin allows unauthenticated attackers to bypass file type validation and upload malicious PHP files through the bug report submission feature, potentially leading to remote code execution on the affected WordPress site.

Is CVE-2024-5450 being actively exploited?

No, CVE-2024-5450 is not currently listed in the CISA Known Exploited Vulnerabilities catalog, and no public exploits have been disclosed, but the critical CVSS score warrants immediate patching.

What versions of the Bug Library plugin are affected by CVE-2024-5450?

All versions prior to 2.1.1 are vulnerable; the exact earliest affected version is unknown, so it is recommended to update any installation below 2.1.1.

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

Navigate to Plugins in the WordPress admin dashboard and locate 'Bug Library'—if the version is below 2.1.1, your site is vulnerable. Alternatively, use WP-CLI: wp plugin list --allow-root | grep 'bug-library'

Does Defensia detect CVE-2024-5450?

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

Get started free