CVE-2026-1251

SupportCandy – Helpdesk & Customer Support Ticket System <= 3.4.4 - Authenticated (Subscriber+) Insecure Direct Object Reference

2026-01-23 00:00
Theklis

Strategic Overview

Status
Patched in 3.4.5
Affected Plugin
SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent
Affected Version
<= 3.4.4
CVSS
5.4Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-1251
View all SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent vulnerabilities

At a glance

CVE-2026-1251 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the SupportCandy WordPress plugin, affecting versions <= 3.4.4. 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 3.4.5; sites on affected versions should update now. Disclosed January 2026, reported by Theklis.

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.4.4 via the 'add_reply' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to steal file attachments uploaded by other users by specifying arbitrary attachment IDs in the 'description_attachments' parameter, re-associating those files to their own tickets and removing access from the original owners.

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-639: Authorization Bypass Through User-Controlled Key

SupportCandy <= 3.4.4 carries this weakness at add_reply, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For SupportCandy the fix is 3.4.5: builds <= 3.4.4 are affected, anything from 3.4.5 onward is not.

Remediation

Update to version 3.4.5, 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.4.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1251https://www.wordfence.com/threat-intel/vulnerabilities/id/89df3005-0967-474f-8a4e-3b23273dd1a2https://nvd.nist.gov/vuln/detail/CVE-2026-1251

Related records

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