dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2018-0118

MEDIUM · 6.1 CVSS v3.0 Published 2018-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A vulnerability in the web-based management interface of Cisco Unified Communications Manager could allow an unauthenticated, remote attacker to perform a cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected device. An attacker could exploit this vulnerability by persuading a user of the web-based management interface to click a link that is designed to submit malicious input to the interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information on the targeted device. Cisco Bug IDs: CSCvg51264.

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 confidence

Cisco Unified Communications Manager web-based management interface contains a stored XSS vulnerability due to insufficient validation of user-supplied input. An unauthenticated, remote attacker can exploit this by tricking a user into clicking a malicious link that submits crafted input to the interface, allowing arbitrary JavaScript execution in the user's browser context or access to sensitive browser-based information.

MitigationApply the Cisco patch for CSCvg51264. Until patched, users should avoid clicking untrusted links to the management interface. Consider deploying a web application firewall (WAF) as an interim control.

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
Unified Communications ManagerApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CUCM web management interface exposure
    Determine if the Cisco Unified Communications Manager web interface is accessible on your network. This is typically accessible via HTTPS on port 8443 or 443. Check your firewall rules and network scans for devices responding on these ports with a Cisco Unified Communications Manager login page.
    Affected if The CUCM web interface is accessible from a network where untrusted users could potentially send malicious links to management users.
  2. Confirm the installed CUCM version
    Log into the Cisco Unified Communications Manager administration interface and navigate to About > Version Information, or run the 'show version' command via the CUCM CLI to identify the exact version installed.
    Affected if Any version of Cisco Unified Communications Manager is listed, as all versions are affected by this vulnerability.
  3. Review web interface logs for XSS indicators
    Examine CUCM web logs (such as Tomcat access logs or Cisco Tomcat logs) for suspicious JavaScript payload patterns, such as <script> tags, javascript: URIs, or event handler attributes like onerror, onload within request parameters.
    Affected if Any entries containing XSS payload patterns are found in the web interface logs, indicating potential exploitation attempts.
  4. Check for CSCvg51264 patch installation
    In the CUCM administration interface, navigate to Cisco Unified Reporting > System Reports > Software Upgrades > Install History, or use the CLI command 'show version active' to identify installed patches. Look for patch ID CSCvg51264 in the installed patches list.
    Affected if The patch CSCvg51264 is NOT listed among installed patches, meaning the vulnerability remains unmitigated.

Your environment is affected if Cisco Unified Communications Manager web interface is accessible and the CSCvg51264 patch has not been installed, regardless of the specific CUCM version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco patch for CSCvg51264. Until patched, users should avoid clicking untrusted links to the management interface. Consider deploying a web application firewall (WAF) as an interim control.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
11.0 hours of engineering $2,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-0118 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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