CVE-2019-13076
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 · uneditedQuest KACE Systems Management Appliance Server Center 9.1.317 is vulnerable to SQL injection. An authenticated user has the ability to execute arbitrary commands against the database. The affected component is /userui/ticket_list.php, and affected parameters are order[0][column] and order[0][dir].
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 confidenceQuest KACE Systems Management Appliance Server Center 9.1.317 contains a SQL injection vulnerability in /userui/ticket_list.php. Authenticated attackers can inject malicious SQL code through the order[0][column] and order[0][dir] parameters to execute arbitrary commands against the underlying database.
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= 9.1.317CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Quest KACE SMA installationIdentify if Quest KACE Systems Management Appliance is installed in your environment. This is typically a physical or virtual appliance. Check your asset inventory or documentation for KACE SMA presence.Affected if Quest KACE Systems Management Appliance is present in the environment
-
Check installed KACE SMA versionAccess the KACE SMA administrative interface and navigate to the System Overview or About section to view the exact version number. Alternatively, check system documentation or appliance management console for the installed version.Affected if The installed version is exactly 9.1.317
-
Verify access to ticket_list.phpConfirm that the /userui/ticket_list.php endpoint is accessible. This requires valid authentication to the KACE SMA web interface. Try accessing the URL or check web server logs for requests to this endpoint.Affected if The /userui/ticket_list.php endpoint is accessible with valid credentials
-
Inspect order parameter handlingIf you have access to logs or can test the application, examine how the order[0][column] and order[0][dir] parameters are processed in ticket_list.php. These parameters control sorting in the ticket list view.Affected if The application accepts user input in order[0][column] or order[0][dir] parameters without proper input validation or parameterized queries
You are affected if you are running exactly version 9.1.317 of Quest KACE Systems Management Appliance and have authenticated access to the web interface where the ticket_list.php endpoint processes sorting parameters.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied patch or upgrade to a patched version of KACE SMA. As an interim control, implement strict input validation on the order parameters and consider deploying a WAF rule to detect and block SQL injection attempts.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13076 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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