CVE-2017-15362
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 · uneditedosTicket 1.10.1 allows arbitrary client-side JavaScript code execution on victims who click a crafted support/scp/tickets.php?status= link, aka XSS. Session ID and data theft may follow as well as the possibility of bypassing CSRF protections, injection of iframes to establish communication channels, etc. The vulnerability is present after login into the application. This affects a different tickets.php file than CVE-2015-1176.
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 confidenceosTicket 1.10.1 contains a reflected XSS vulnerability in the tickets.php file where the 'status' GET parameter is not properly sanitized before being reflected in the HTML output. Attackers can craft malicious URLs that, when clicked by authenticated users, execute arbitrary JavaScript in the victim's browser, potentially leading to session hijacking, CSRF token theft, or further injection attacks.
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= 1.10.1CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify osTicket versionCheck the version of osTicket installed in your environment. This is typically found in the admin panel under System Information, or by inspecting the include/ost-config.php file or a VERSION file in the installation directory.Affected if The installed version is exactly 1.10.1. Earlier versions (e.g., 1.10, 1.9.x) or later versions (e.g., 1.10.2+) are not affected by this specific CVE.
-
Locate tickets.php fileVerify that the tickets.php file exists in your osTicket web root directory. This file is part of the client-facing ticket viewing interface.Affected if The file exists and is accessible via the web. If the file has been removed or renamed, the attack surface may be reduced.
-
Check if 'status' parameter is processedExamine the tickets.php file for code that handles the 'status' GET parameter. Look for lines where $_GET['status'] or similar superglobal is used without sanitization.Affected if The code reads the 'status' parameter directly from $_GET and outputs it into HTML without escaping functions like htmlspecialchars() or similar.
-
Test for reflected XSSCraft a test URL such as /tickets.php?status=<script>alert('XSS')</script> and access it while authenticated. If an alert box executes, the vulnerability is present.Affected if The JavaScript executes in the browser, indicating the 'status' parameter is being reflected without proper output encoding.
You are affected if you are running osTicket version 1.10.1 and the tickets.php file processes the 'status' GET parameter without sanitization, allowing script injection.
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 for all user-supplied parameters, specifically the 'status' parameter in tickets.php, using context-appropriate escaping functions to neutralize malicious script content.
- Consultation2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15362 — 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-2017-15362 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