CVE-2024-10627

WooCommerce Support Ticket System <= 17.7 - Unauthenticated Arbitrary File Upload

2024-11-08 00:00
Tonn

Strategic Overview

Status
Patched in 17.8
Affected Version
<= 17.7
CVSS
9.8Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2024-10627
View all WooCommerce Support Ticket System vulnerabilities

At a glance

CVE-2024-10627 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WooCommerce Support Ticket System WordPress plugin, affecting versions <= 17.7. 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 17.8; sites on affected versions should update now. Disclosed November 2024, reported by Tonn.

Vulnerability Overview

The WooCommerce Support Ticket System plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ajax_manage_file_chunk_upload() function in all versions up to, and including, 17.7. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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

WooCommerce Support Ticket System <= 17.7 carries this weakness at ajax_manage_file_chunk_upload(), and reaching it 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 WooCommerce Support Ticket System the fix is 17.8: builds <= 17.7 are affected, anything from 17.8 onward is not.

Remediation

Update to version 17.8, 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: WooCommerce Support Ticket System 17.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

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