CVE-2021-24843

SupportCandy <= 2.2.6 - Cross-Site Request Forgery to Arbitrary Ticket Deletion

2022-01-04 00:00
apple502j

Strategic Overview

Status
Patched in 2.2.7
Affected Plugin
SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent
Affected Version
< 2.2.7
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-24843
View all SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent vulnerabilities

At a glance

CVE-2021-24843 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the SupportCandy WordPress plugin, affecting versions < 2.2.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.2.7; sites on affected versions should update now. Disclosed January 2022, reported by apple502j.

Vulnerability Overview

The SupportCandy WordPress plugin before 2.2.7 does not have CRSF check in its wpsc_tickets AJAX action, which could allow attackers to make a logged in admin call it and delete arbitrary tickets via the set_delete_permanently_bulk_ticket setting_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 privileges on the target site. A successful exploit has high impact on integrity.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in SupportCandy < 2.2.7 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For SupportCandy the fix is 2.2.7: builds < 2.2.7 are affected, anything from 2.2.7 onward is not.

Remediation

Update to version 2.2.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to SupportCandy: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SupportCandy 2.2.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24843https://www.wordfence.com/threat-intel/vulnerabilities/id/9e1fa691-3934-4e15-b339-e679976d6d5chttps://nvd.nist.gov/vuln/detail/CVE-2021-24843

Related records

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