WooCommerce Upload Files < 59.4 - Unauthenticated Arbitrary File Upload
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-434.
Summary
The WooCommerce Upload Files WordPress plugin before 59.4 ran a single sanitization pass to remove blocked extensions such as .php. It was possible to bypass this and upload a file with a PHP extension by embedding a "blocked" extension within another "blocked" extension in the "wcuf_file_name" parameter. It was also possible to perform a double extension attack and upload files to a different location via path traversal using the "wcuf_current_upload_session_id" parameter.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | WooCommerce Upload Files | 59.4 to before 59.4 | 59.4 | Patch available | CNA |
- WooCommerce Upload Files VendorUnknown Affected 59.4 to before 59.4 Fixed in 59.4 Patch available CNA
Remediation
- Fix · CNA WooCommerce Upload Files (Unknown) Fixed in 59.4
Timeline
- 2026-10-02 Threatist record created from CVE-2021-24171
- 2026-10-03 Alias added: GHSA-73q3-2843-4j2x
References
More vanquish Woocommerce Upload Files vulnerabilities
- TI-2024-10031 WooCommerce Upload Files <= 84.3 - Unauthenticated Arbitrary File Upload CVSS 3.1CRITICAL 9.8
Sources
- CVE-2021-24171 · CVE Program
- CVE-2021-24171 · NVD
- FIRST EPSS
- GHSA-73q3-2843-4j2x · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences