LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0683: SupportCandy – Helpdesk & Customer Support Ticket System <= 3.4.4 - Authenticated (Subscriber+) SQL Injection via Number Field Filter

The SupportCandy – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to SQL Injection via the Number-type custom field filter in all versions up to, and including, 3.4.4. This is due to insufficient escaping on the user-supplied operand value when using the equals operator and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above (customers), to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0683 affects the WordPress SupportCandy helpdesk plugin through version 3.4.4. A logged-in low-privilege user, such as a subscriber or customer, may be able to read sensitive database information through a vulnerable ticket filter. This is not listed as actively exploited in the provided sources.

Executive priority

Treat as a prompt remediation item for WordPress sites using SupportCandy with customer logins. The business risk is potential exposure of sensitive database content by authenticated users, but current sources do not support emergency active-exploitation handling.

Technical view

The flaw is SQL injection in the Number-type custom field filter when the equals operator is used. The source describes insufficient escaping of a user-supplied operand and insufficient query preparation. CVSS 3.1 is 6.5: network-accessible, low complexity, low privileges, no user interaction, high confidentiality impact.

Likely exposure

Exposure is likely for WordPress sites running SupportCandy Helpdesk versions up to and including 3.4.4, especially where customers or subscribers can authenticate and use ticket filtering features.

Exploitation context

An attacker needs an authenticated account with Subscriber-level access or higher. The reported impact is database information disclosure, not code execution, data modification, or service disruption. No KEV listing or cited source indicates active exploitation.

Researcher notes

Key review areas are the Number custom field filter, equals operator handling, and SQL query preparation in the referenced SupportCandy files. The WordPress changeset is relevant for understanding the vendor-side correction, but the provided bundle does not name a specific fixed release.

Mitigation direction

  • Identify all WordPress sites running the SupportCandy plugin.
  • Upgrade SupportCandy to a version newer than 3.4.4 if available.
  • If no update is available, check vendor and WordPress plugin guidance.
  • Restrict untrusted authenticated access to ticket filtering features where feasible.
  • Review whether open registration creates unnecessary low-privilege attacker access.

Validation and detection

  • Confirm installed SupportCandy versions across WordPress assets.
  • Verify whether any instance is version 3.4.4 or earlier.
  • Review roles allowed to access SupportCandy ticket filters.
  • Check application logs for unusual authenticated ticket-filter activity.
  • Confirm remediation by verifying the plugin version after update.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0683 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-0683Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
psmpluginsSupportCandy – Helpdesk & Customer Support Ticket System0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.