dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-0683

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SupportCandy WordPress helpdesk plugin fails to properly sanitize and escape user-supplied operand values in Number-type custom field filters when using the equals operator. Combined with insufficient prepared statement usage, this allows authenticated users with Subscriber-level access to inject arbitrary SQL queries and exfiltrate data from the database.

MitigationUpdate the SupportCandy plugin to the latest version beyond 3.4.4 where the vendor has addressed the SQL injection vulnerability. If immediate update is not possible, consider restricting access to the affected filter functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SupportCandy plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate SupportCandy in the installed plugins list
    Affected if SupportCandy plugin is present in the WordPress installation
  2. Identify installed plugin version
    In the Plugins list, view the version number displayed under the SupportCandy plugin name
    Affected if Version is below 3.4.4 (or version cannot be determined and plugin is present)
  3. Check for Number-type custom fields
    Go to SupportCandy settings > Custom Fields and review the field types configured; look for fields with type set to Number
    Affected if One or more Number-type custom fields exist in the helpdesk configuration
  4. Verify Subscriber role access to filtering
    Review WordPress user roles and SupportCandy permissions to confirm Subscriber-level users can access the ticket filter functionality
    Affected if Subscriber role or any authenticated user role has permission to use custom field filters with the equals operator

User is affected if SupportCandy plugin is installed with a version below 3.4.4 AND Number-type custom fields are configured AND Subscriber-level users have access to filter functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the SupportCandy plugin to the latest version beyond 3.4.4 where the vendor has addressed the SQL injection vulnerability. If immediate update is not possible, consider restricting access to the affected filter functionality.

Recommended fix Moderate confidence

Version 3.4.5 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the SupportCandy – Helpdesk & Customer Support Ticket System plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version (version 3.4.5 or higher)
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly and test the Number-type custom field filter to confirm the SQL injection vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0683 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data