CVE-2019-13078
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 /common/user_profile.php. The affected parameter is sort_column.
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 · moderate confidenceQuest KACE Systems Management Appliance Server Center 9.1.317 contains a SQL injection vulnerability in /common/user_profile.php via the sort_column parameter. An authenticated user can exploit this to execute arbitrary SQL commands against the database, potentially leading to data exfiltration, modification, or complete database compromise.
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.
-
Verify Quest KACE SMA installationAccess the appliance admin interface or check system information to confirm the product is Quest KACE Systems Management Appliance Server Center.Affected if The installed product is Quest KACE Systems Management Appliance Server Center.
-
Check installed version numberNavigate to the appliance's system settings or about page to determine the exact version. Alternatively, check the version via the API or system files if accessible.Affected if The installed version is exactly 9.1.317.
-
Confirm vulnerable file existsVerify that /common/user_profile.php is present on the web server. This may require file system access or attempting to access the URL endpoint.Affected if The file /common/user_profile.php exists and is accessible via the web interface.
-
Check authentication accessDetermine if valid user credentials exist for the appliance. The SQL injection requires an authenticated session.Affected if You have valid user credentials to log into the KACE SMA.
-
Identify sort_column parameter usageReview the request handling in user_profile.php or test the parameter by observing application behavior when the sort_column parameter is manipulated in requests.Affected if The sort_column parameter is accepted and processed by the user_profile.php endpoint.
You are affected if the installed version is exactly 9.1.317, the /common/user_profile.php file exists, you have valid authentication credentials, and the sort_column parameter is actively used by the application.
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 the vendor patch when available. As an interim measure, implement strict input validation on the sort_column parameter and refactor the vulnerable query to use parameterized queries or prepared statements.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13078 — 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-13078 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