CVE-2024-13775

WooCommerce Support Ticket System <= 17.8 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Deletion and Information Exposure

2025-01-31 00:00
Lucio Sá

Strategic Overview

Status
Patched in 17.9
Affected Version
<= 17.8
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-13775
View all WooCommerce Support Ticket System vulnerabilities

At a glance

CVE-2024-13775 is a medium-severity Missing Authorization vulnerability in the WooCommerce Support Ticket System WordPress plugin, affecting versions <= 17.8. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 17.9; sites on affected versions should update now. Disclosed January 2025, reported by Lucio Sá.

Vulnerability Overview

The WooCommerce Support Ticket System plugin for WordPress is vulnerable to unauthorized access and loss of data due to missing capability checks on the 'ajax_delete_message', 'ajax_get_customers_partial_list', and 'ajax_get_admins_list' functions in all versions up to, and including, 17.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary posts, and read names, emails, and capabilities of all users.

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 interaction from a victim user.

CWE-862: Missing Authorization

WooCommerce Support Ticket System <= 17.8 carries this weakness at ajax_delete_message, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WooCommerce Support Ticket System the fix is 17.9: builds <= 17.8 are affected, anything from 17.9 onward is not.

Remediation

Update to version 17.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WooCommerce Support Ticket System 17.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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