CVE-2024-13552

SupportCandy – Helpdesk & Customer Support Ticket System <= 3.3.0 - Insecure Direct Object Reference

2025-03-06 20:26
Tim Coen

Strategic Overview

Status
Patched in 3.3.1
Affected Version
<= 3.3.0
CVSS
4.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2024-13552
View all SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent vulnerabilities

At a glance

CVE-2024-13552 is a medium-severity Improper Authorization vulnerability in the SupportCandy WordPress plugin, affecting versions <= 3.3.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 3.3.1; sites on affected versions should update now. Disclosed March 2025, reported by Tim Coen.

Vulnerability Overview

The SupportCandy – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.3.0 via file upload due to missing validation on a user controlled key. This makes it possible for authenticated attackers to download attachments for support tickets that don't belong to them. If an admin enables tickets for guests, this can be exploited by unauthenticated attackers.

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-285: Improper Authorization

Reaching this weakness in SupportCandy <= 3.3.0 takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For SupportCandy the fix is 3.3.1: builds <= 3.3.0 are affected, anything from 3.3.1 onward is not.

Remediation

Update to version 3.3.1, 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: SupportCandy 3.3.1 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