CVE-2019-13081
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 has an XSS vulnerability (via the title field in the /common/ticket_associated_tickets.php service desk ticket functionality) that allows an authenticated user to execute arbitrary JavaScript in a service desk user's browser.
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 stored XSS vulnerability in the title field of /common/ticket_associated_tickets.php within the service desk ticket functionality. An authenticated attacker can inject malicious JavaScript that executes in the browser of other service desk users who view the affected ticket.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify KACE SMA versionAccess the KACE SMA admin interface and navigate to the System Settings or About page to confirm the installed version is exactly 9.1.317Affected if Version displayed is 9.1.317 exactly
-
Confirm service desk is enabledLog into the KACE SMA administrative console and check if the Service Desk module is provisioned and accessible to usersAffected if Service Desk functionality is active and users can create or view tickets
-
Identify the vulnerable endpointLocate the file /common/ticket_associated_tickets.php within the KACE SMA web root directoryAffected if The file exists and is accessible via the web interface
-
Inspect ticket title fields for XSS payloadsQuery the database or examine ticket records in the Service Desk interface, specifically looking at the title field values in associated tickets for suspicious script tags or HTMLAffected if Any ticket contains unsanitized script content in the title field that could execute in another user's browser
-
Review user browser behaviorAs a different user account, navigate to view a ticket that may contain a crafted title and observe if JavaScript executes in the browser contextAffected if JavaScript code in the ticket title executes when viewing the affected ticket
You are affected if your Quest KACE Systems Management Appliance is exactly version 9.1.317 and the Service Desk module is enabled, allowing authenticated users to create tickets with malicious title field content that executes for other users viewing those tickets.
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 dataImplement proper input validation and output encoding/sanitization on the title field in ticket_associated_tickets.php to prevent script injection. Consider implementing a Content Security Policy (CSP) as defense-in-depth.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13081 — 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-13081 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