CVE-2024-3962

Product Addons & Fields for WooCommerce <= 32.0.18 - Unauthenticated Arbitrary File Upload via ppom_upload_file

2024-04-25 00:00
andrea bocchetti

Strategic Overview

Status
Patched in 32.0.19
Affected Plugin
PPOM – Product Addons & Custom Fields for WooCommerce
Affected Version
<= 32.0.18
CVSS
9.8Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2024-3962
View all PPOM – Product Addons & Custom Fields for WooCommerce vulnerabilities

At a glance

CVE-2024-3962 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the PPOM WordPress plugin, affecting versions <= 32.0.18. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 32.0.19; sites on affected versions should update now. Disclosed April 2024, reported by andrea bocchetti.

Vulnerability Overview

The Product Addons & Fields for WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ppom_upload_file function in all versions up to, and including, 32.0.18. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. Successful exploitation requires the PPOM Pro plugin to be installed along with a WooCommerce product that contains a file upload field to retrieve the correct nonce.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in PPOM <= 32.0.18 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For PPOM the fix is 32.0.19: builds <= 32.0.18 are affected, anything from 32.0.19 onward is not.

Remediation

Update to version 32.0.19, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: PPOM 32.0.19 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2024-3962https://www.wordfence.com/threat-intel/vulnerabilities/id/4f95bcc3-354e-4016-9a17-945569b076b6https://nvd.nist.gov/vuln/detail/CVE-2024-3962

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C