dbcve.org
Security CenterApplication · Tenable

CVE-2026-64877

HIGH · 8.4 CVSS v3.1 Published 2026-07-21
Fix available
A fix is available. Upgrade to after 6.8.0 or later.
See remediation →
86/100
Remediation priority · High
Zero-click 4 weeks old

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
An authenticated non-admin user can exploit a SQL injection flaw in the ticketing REST API to access sensitive data stored in the appliance 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

An authenticated non-admin user can exploit a SQL injection flaw in the ticketing REST API to access sensitive data stored in the appliance database. The vulnerability exists in the API layer handling ticketing operations, where user input is not properly parameterized before being passed to database queries.

MitigationImplement parameterized queries or prepared statements for all database operations in the ticketing REST API, and enforce least-privilege access controls to limit what authenticated users can query.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Security CenterApplication
Affected:>= 6.6.0, <= 6.8.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/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. Identify if ticketing REST API is enabled
    Locate the application configuration files or service settings and search for entries related to ticketing REST API functionality (e.g., 'ticketing', 'ticket', 'REST', 'api'). Confirm the API module is present and active.
    Affected if The ticketing REST API feature is installed and enabled in the environment
  2. Verify API authentication is configured
    Review the authentication settings for the ticketing REST API. Check if basic or standard user accounts are permitted to authenticate against the API endpoints.
    Affected if Non-admin user accounts can successfully authenticate to the ticketing REST API
  3. Locate ticketing API endpoint definitions
    Examine the API route configuration or service definitions for endpoints handling ticketing operations. Identify the specific URL paths or route handlers that process ticket-related requests.
    Affected if Ticketing REST API endpoints are exposed and accessible in the application
  4. Inspect API parameter handling for input validation
    Review the source code or configuration of the ticketing API handlers. Look for database query construction that uses user-supplied parameters without visible sanitization, parameter binding, or input validation routines.
    Affected if API parameters are processed directly into SQL queries without recognized sanitization or parameterized query implementation
  5. Check database access permissions for non-admin API users
    Review database role configurations or application permission settings to determine what data non-admin API users can access through the ticketing endpoint.
    Affected if Non-admin API users have direct database query access that could allow data extraction
  6. Compare installed application version to vendor release timeline
    Locate the installed application version string through system inventory, about pages, or version APIs. If vendor has published affected version ranges for CVE-2026-64877, compare your version against those ranges.
    Affected if The installed version falls within an affected range if published by the vendor

Your environment is affected if the ticketing REST API is enabled and permits non-admin user authentication without proper input sanitization on API parameters used in database queries.

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.

From vendor data
Upgrade available Upgrade to a release after 6.8.0
Interim mitigation

Implement parameterized queries or prepared statements for all database operations in the ticketing REST API, and enforce least-privilege access controls to limit what authenticated users can query.

Fix this in Security Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-64877 — 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-64877 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