Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-13744: CWE-434 Unrestricted Upload of File with Dangerous Type in pluggabl Booster for WooCommerce

0
High
VulnerabilityCVE-2024-13744cvecve-2024-13744cwe-434
Published: Fri Apr 04 2025 (04/04/2025, 04:21:22 UTC)
Source: CVE Database V5
Vendor/Project: pluggabl
Product: Booster for WooCommerce

Description

CVE-2024-13744 is a high-severity vulnerability in the Booster for WooCommerce WordPress plugin versions 4. 0. 1 to 7. 2. 4. It allows unauthenticated attackers to upload arbitrary files due to missing file type validation in the validate_product_input_fields_on_add_to_cart function. This unrestricted file upload can lead to remote code execution on the affected server. The vulnerability does not require authentication or user interaction but has a high attack complexity. No known exploits are currently reported in the wild. Organizations using this plugin for WooCommerce are at risk of severe confidentiality, integrity, and availability impacts.

AI-Powered Analysis

AILast updated: 02/25/2026, 22:12:48 UTC

Technical Analysis

CVE-2024-13744 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) found in the Booster for WooCommerce plugin for WordPress, specifically in versions 4.0.1 through 7.2.4. The flaw exists in the validate_product_input_fields_on_add_to_cart function, which fails to properly validate the type of files uploaded by users. This lack of validation allows unauthenticated attackers to upload arbitrary files, including potentially malicious scripts, to the web server hosting the affected WordPress site. Because the plugin is widely used to extend WooCommerce functionality, this vulnerability presents a critical risk. Exploiting this vulnerability could enable remote code execution (RCE), allowing attackers to execute arbitrary commands on the server, escalate privileges, steal sensitive data, or disrupt service availability. The CVSS v3.1 score of 8.1 reflects the high impact on confidentiality, integrity, and availability, combined with the fact that no privileges or user interaction are required, though the attack complexity is high. While no known exploits have been reported in the wild yet, the vulnerability's nature makes it a prime target for attackers once exploit code becomes available. The absence of patch links suggests that a fix may not yet be publicly released, increasing the urgency for mitigation.

Potential Impact

The impact of CVE-2024-13744 is significant for organizations using the Booster for WooCommerce plugin. Successful exploitation can lead to remote code execution, allowing attackers to gain full control over the affected web server. This can result in data breaches, theft of customer information, defacement of websites, insertion of malware or ransomware, and disruption of e-commerce operations. The compromise of WooCommerce stores can damage brand reputation and cause financial losses. Because the vulnerability is exploitable without authentication, any internet-facing WooCommerce site using the vulnerable plugin is at risk. The high attack complexity somewhat limits mass exploitation but does not eliminate the threat, especially from skilled attackers targeting high-value e-commerce sites. The broad use of WooCommerce globally means that many organizations, from small businesses to large enterprises, could be affected, amplifying the potential global impact.

Mitigation Recommendations

To mitigate CVE-2024-13744, organizations should immediately verify if they are running affected versions (4.0.1 to 7.2.4) of the Booster for WooCommerce plugin. If so, they should monitor the vendor’s official channels for patches or updates and apply them as soon as they become available. In the absence of an official patch, administrators should consider temporarily disabling the plugin or restricting file upload functionality via web application firewall (WAF) rules to block suspicious file types and upload attempts. Implementing strict server-side file type validation and limiting upload directories to non-executable locations can reduce risk. Additionally, monitoring web server logs for unusual upload activity and scanning for web shells or unauthorized files is critical. Employing least privilege principles on the web server and isolating the WordPress environment can help contain potential exploitation. Regular backups and incident response plans should be updated to prepare for potential compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-27T18:04:36.322Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e6cb7ef31ef0b5a05f3

Added to database: 2/25/2026, 9:49:32 PM

Last enriched: 2/25/2026, 10:12:48 PM

Last updated: 2/26/2026, 6:09:20 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats