CVE-2026-54826

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

2026-06-17 00:00
HieuPenguinnn

Strategic Overview

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

At a glance

CVE-2026-54826 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the SupportCandy WordPress plugin, affecting versions <= 3.4.6. It carries a CVSS score of 4.3 (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.7; sites on affected versions should update now. Disclosed June 2026, reported by HieuPenguinnn.

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.6 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.

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

Reaching this weakness in SupportCandy <= 3.4.6 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.7: builds <= 3.4.6 are affected, anything from 3.4.7 onward is not.

Remediation

Update to version 3.4.7, 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.7 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-54826https://www.wordfence.com/threat-intel/vulnerabilities/id/cf2c451d-a30c-4c0f-9cf0-6361f6b1913chttps://nvd.nist.gov/vuln/detail/CVE-2026-54826

Related records

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