CVE-2019-18356
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 · uneditedAn XSS issue was discovered in Thycotic Secret Server before 10.7 (issue 1 of 2).
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 confidenceCross-Site Scripting (XSS) vulnerability in Thycotic Secret Server versions before 10.7 allows attackers to inject malicious scripts into web pages viewed by other users, potentially leading to session hijacking or credential theft.
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< 10.7.000000CVSS 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.1/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 Thycotic Secret Server versionLog into the Secret Server web interface as an administrator. Navigate to Help > About or Admin > Configuration > General Settings to view the installed version number.Affected if The displayed version is below 10.7.000000 (for example, 10.6.x, 10.5.x, etc.)
-
Verify web interface accessibilityConfirm the Secret Server web interface is accessible to users. XSS vulnerabilities in web applications require the web interface to be reachable.Affected if The web interface is accessible and users can input data into web forms or view content rendered by the application
-
Check for user input points in web applicationReview web pages in Secret Server that accept user-supplied input such as search fields, custom templates, folder names, secret naming, or notes fields.Affected if User-accessible input fields exist in the web interface that could accept and render unsanitized content back to users
-
Confirm user roles and accessNavigate to Admin > Users or Admin > Roles to determine if multiple user accounts with different privilege levels exist in the system.Affected if Multiple users or groups have access to view content created by others, enabling stored XSS propagation
-
Review admin configuration for customizationsCheck Admin > Configuration for any enabled custom features, templates, or integrations that allow user-defined content to be displayed.Affected if Custom templates, workflows, or third-party integrations are enabled that handle user-supplied data without additional encoding
You are affected if your installed Thycotic Secret Server version is before 10.7.000000 and the web interface is accessible to multiple users who can input or view content that may not be properly sanitized.
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 data10.7.000000
Upgrade Thycotic Secret Server to version 10.7 or later. Apply input validation and output encoding to user-supplied data in affected components.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18356 — 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-18356 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