CVE-2026-81022: CWE-200 Information Exposure in SupportCandy
Affects SupportCandySource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 3.5.3 : update SupportCandy when convenient.
Data as of 10/25/2026, 04:40:14 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SupportCandy | Affected
| Fixed in
|
AI-suggested
A fixed version is available starting from SupportCandy 3.5.3. Users should upgrade to version 3.5.3 or later to remediate this vulnerability. Patch status is not explicitly confirmed in the input data, but the affected versions indicate the fix is in 3.5.3. No other mitigation steps are provided or required.
Description
The SupportCandy WordPress plugin before 3.5.3 does not validate a submitted per-ticket authorization code before disclosing the real code to the requester, allowing unauthenticated users to read the contents of any support ticket.
Impact
An unauthenticated attacker can read the contents of any support ticket in the affected versions of the SupportCandy plugin. This leads to unauthorized disclosure of potentially sensitive information contained within support tickets. There is no impact on integrity or availability reported.
Weaknesses
- CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.