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-13359: CWE-434 Unrestricted Upload of File with Dangerous Type in tychesoftwares Product Input Fields for WooCommerce

0
High
VulnerabilityCVE-2024-13359cvecve-2024-13359cwe-434
Published: Sat Mar 08 2025 (03/08/2025, 09:22:53 UTC)
Source: CVE Database V5
Vendor/Project: tychesoftwares
Product: Product Input Fields for WooCommerce

Description

CVE-2024-13359 is a high-severity vulnerability in the Product Input Fields for WooCommerce WordPress plugin that allows unauthenticated attackers to upload arbitrary files due to insufficient file type validation. The vulnerability exists in all versions up to and including 1. 12. 0 and can lead to remote code execution, especially if administrators misconfigure accepted file extensions. By default, the plugin is vulnerable to double extension file uploads, which can bypass restrictions. The vulnerability is rooted in CWE-434: Unrestricted Upload of File with Dangerous Type. No known exploits are currently reported in the wild. This flaw poses a significant risk to websites using this plugin, potentially compromising confidentiality, integrity, and availability. Patch versions 1. 12.

AI-Powered Analysis

AILast updated: 02/26/2026, 01:25:55 UTC

Technical Analysis

The Product Input Fields for WooCommerce plugin, widely used in WordPress e-commerce sites, suffers from a critical file upload vulnerability identified as CVE-2024-13359. The root cause lies in the add_product_input_fields_to_order_item_meta() function, which fails to adequately validate file types during uploads. This allows unauthenticated attackers to upload arbitrary files, including potentially malicious scripts. By default, the plugin restricts direct .php uploads, but attackers can exploit double extension techniques (e.g., file.php.jpg) to bypass these checks. If an administrator misconfigures the accepted file extensions by leaving the field blank, direct .php file uploads become possible, significantly increasing risk. Successful exploitation can lead to remote code execution on the server, compromising the entire website and backend systems. The vulnerability affects all versions up to and including 1.12.0. Although version 1.12.2 was mistakenly marked as patched, the correct patched version is 1.12.1. The CVSS v3.1 score is 8.1, reflecting high impact on confidentiality, integrity, and availability with no authentication or user interaction required, but with a high attack complexity. No known exploits have been reported in the wild yet, but the potential for severe damage is substantial given the plugin’s widespread use in WooCommerce environments.

Potential Impact

This vulnerability can have severe consequences for organizations using the affected plugin. An attacker could upload malicious files leading to remote code execution, enabling full compromise of the web server. This can result in data theft, website defacement, insertion of backdoors, pivoting to internal networks, and disruption of e-commerce operations. The confidentiality of customer data and payment information could be breached, damaging reputation and leading to regulatory penalties. The integrity of the website content and transactional data can be undermined, and availability may be impacted by denial-of-service conditions caused by malicious payloads. Since the vulnerability requires no authentication or user interaction, it is highly exploitable remotely, increasing the risk of widespread attacks. Organizations relying on WooCommerce for online sales are particularly at risk, as attackers may target these sites for financial gain or to leverage compromised infrastructure for further attacks.

Mitigation Recommendations

Organizations should immediately verify the version of the Product Input Fields for WooCommerce plugin and upgrade to version 1.12.1 or later, which contains the fix. Administrators must ensure that the accepted file extensions field is never left blank to prevent direct upload of dangerous file types like .php. Implement strict server-side validation of uploaded files, including MIME type checks and file content inspection, beyond relying solely on file extensions. Employ web application firewalls (WAFs) with rules to detect and block suspicious file upload patterns, including double extensions. Restrict file upload directories with appropriate permissions and disable execution rights on upload folders to prevent execution of uploaded scripts. Regularly audit and monitor upload directories for unauthorized files. Additionally, maintain up-to-date backups and have incident response plans ready in case of compromise. Educate administrators on secure plugin configuration and the risks of improper file upload settings.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-13T16:27:00.061Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e51b7ef31ef0b59e2e2

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

Last enriched: 2/26/2026, 1:25:55 AM

Last updated: 2/26/2026, 6:13:10 AM

Views: 2

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