WordPress security by component
Product Input Fields for WooCommerce
Plugin description
Product Input Fields for WooCommerce is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Mar 08, 2025; the highest CVE/CNA score is 8.1.
Plugin slug:
product-input-fields-for-woocommerceLatest vulnerability
CVE-2024-13359: Product Input Fields for WooCommerce: Dangerous file upload
Product Input Fields for WooCommerce is affected by dangerous file upload. The vulnerable path is reachable without authentication. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
| Safe version |
|
||
|---|---|---|---|
| Mar 08, 2025 |
CVE-2024-13359
Product Input Fields for WooCommerce: Dangerous file upload
Product Input Fields for WooCommerce is affected by dangerous file upload. The vulnerable path is reachable without authentication. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
|
See mitigation notes |
CVE8.1
NVD9.8
|
| Nov 26, 2024 |
CVE-2024-10857
Product Input Fields for WooCommerce: Filesystem traversal
Product Input Fields for WooCommerce is affected by filesystem traversal. Exploitation requires at least contributor-level access. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Apr 15, 2024 |
CVE-2024-31431
Product Input Fields for WooCommerce: Cross-site request forgery
Product Input Fields for WooCommerce is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Jun 07, 2023 |
CVE-2020-36696
Product Input Fields for WooCommerce: A security weakness
Product Input Fields for WooCommerce is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE7.5
NVD7.5
|