CVE-2021-24839

SupportCandy <= 2.2.4 - Unauthenticated Arbitrary Ticket Deletion

2022-01-05 00:00
Brandon James Roldan (tomorrowisnew)

Strategic Overview

Status
Patched in 2.2.5
Affected Plugin
SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent
Affected Version
<= 2.2.4
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2021-24839
View all SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent vulnerabilities

At a glance

CVE-2021-24839 is a high-severity Missing Authorization vulnerability in the SupportCandy WordPress plugin, affecting versions <= 2.2.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.2.5; sites on affected versions should update now. Disclosed January 2022, reported by Brandon James Roldan (tomorrowisnew).

Vulnerability Overview

The SupportCandy WordPress plugin before 2.2.5 does not have authorisation and CSRF checks in its wpsc_tickets AJAX action, which could allow unauthenticated users to call it and delete arbitrary tickets via the set_delete_permanently_bulk_ticket setting_action. Other actions may be affected as well.

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 integrity.

CWE-862: Missing Authorization

Reaching this weakness in SupportCandy <= 2.2.4 takes no account at all. 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 SupportCandy the fix is 2.2.5: builds <= 2.2.4 are affected, anything from 2.2.5 onward is not.

Remediation

Update to version 2.2.5, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: SupportCandy 2.2.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-2021-24839https://www.wordfence.com/threat-intel/vulnerabilities/id/653ab9cb-7084-47e4-b5e3-6788fa5d7496https://nvd.nist.gov/vuln/detail/CVE-2021-24839

Related records

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