CVE-2018-6495
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 · uneditedCross-Site Scripting (XSS) in Micro Focus Universal CMDB, version 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, 10.33, 11.0, CMS, version 4.10, 4.11, 4.12, 4.13, 4.14, 4.15.1 and Micro Focus UCMDB Browser, version 4.10, 4.11, 4.12, 4.13, 4.14, 4.15.1. This vulnerability could be remotely exploited to allow Cross-Site Scripting (XSS).
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 confidenceCross-Site Scripting (XSS) vulnerability in Micro Focus Universal CMDB, CMS, and UCMDB Browser web interfaces. An authenticated or unauthenticated attacker can inject malicious JavaScript code through web request parameters that gets stored and executed in the browsers of other users viewing the affected pages, allowing 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= 0.20= 10.21= 10.22= 10.30= 10.31= 10.32= 10.33= 11.0= 4.10= 4.11= 4.12= 4.13= 4.14= 4.15.1= 4.10= 4.11= 4.12= 4.13= 4.14= 4.15.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
- 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.
-
Identify installed Micro Focus productsList installed software or check for Universal CMDB, CMDB Browser, or CMS Server components on the systemAffected if Any of the three affected products (Universal CMDB, CMDB Browser, or CMS Server) are present
-
Check Universal CMDB versionUse product administration console, version file, or command such as 'ucmdb.bat -version' or check installation directory for version manifestAffected if Version equals 0.20, 10.21, 10.22, 10.30, 10.31, 10.32, 10.33, or 11.0
-
Check CMDB Browser versionAccess CMDB Browser login page and view about/info section, or check installation directory for version fileAffected if Version equals 4.10, 4.11, 4.12, 4.13, 4.14, or 4.15.1
-
Check CMS Server versionAccess CMS administration interface or check installation directory for version fileAffected if Version equals 4.10, 4.11, 4.12, 4.13, 4.14, or 4.15.1
-
Verify web interface is accessibleAttempt to access the web interface URLs (typically /ucmdbbrowser or /cms for respective products) from a browserAffected if The web interface is exposed and reachable
You are affected if you have Universal CMDB, CMDB Browser, or CMS Server installed with any of the listed versions AND the web interface is accessible.
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-provided patches for the specific product versions. Implement input validation and output encoding for all user-supplied data in web pages.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6495 — 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-2018-6495 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