SupportCandy <= 3.1.3 - Sensitive Data Exposure

2023-03-28 00:00

Strategic Overview

Status: Patched in 3.1.4
Affected Plugin: SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent
Affected Version: <= 3.1.3
CVSS: 6.5Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE pending

View all SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent vulnerabilities

At a glance

This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the SupportCandy WordPress plugin, affecting versions <= 3.1.3. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.4; sites on affected versions should update now. Disclosed March 2023.

Vulnerability Overview

The SupportCandy plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.1.3. Users seeking support have the option to upload supporting documents which are placed in /wp-content/uploads/wpsc/. If directory listing is enabled, an attacker can obtain a listing of documents in this directory and access documents directly.

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.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in SupportCandy <= 3.1.3 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For SupportCandy the fix is 3.1.4: builds <= 3.1.3 are affected, anything from 3.1.4 onward is not.

Remediation

Update to version 3.1.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: SupportCandy 3.1.4 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/07c0b4c5-d76e-4bdc-87d1-3144a1466c77

Related records

Other vulnerabilities in SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent

CVSS Vector

6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/