dbcve.org
Unified Contact Center ExpressApplication · Cisco

CVE-2016-6425

MEDIUM · 6.1 CVSS v3.0 Published 2016-10-06
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
Cross-site scripting (XSS) vulnerability in Cisco Unified Intelligence Center (CUIC) 8.5.4 through 9.1(1), as used in Unified Contact Center Express 10.0(1) through 11.0(1), allows remote attackers to inject arbitrary web script or HTML via a crafted URL, aka Bug IDs CSCuy75020 and CSCuy81652.

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 confidence

Reflected cross-site scripting (XSS) vulnerability in Cisco Unified Intelligence Center (CUIC) web interface allows remote unauthenticated attackers to inject arbitrary HTML or JavaScript via a crafted URL parameter. The vulnerability stems from insufficient input validation in URL handling, allowing the attacker's script to be reflected back to the user's browser.

MitigationApply the Cisco security patch for CSCuy75020/CSCuy81652 to affected CUIC versions 8.5.4 through 9.1(1) and corresponding Unified Contact Center Express versions 10.0(1) through 11.0(1). As a compensating control, implement Content Security Policy (CSP) headers and validate URL parameters server-side before rendering.

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 Contact Center ExpressApplication
Affected:= 10.0\(1\)= 10.5\(1\)= 10.6\(1\)= 11.0\(1\)
Unified Intelligence CenterApplication
Affected:= 8.5.4= 9.0\(2\)= 9.1\(1\)

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 installed CUIC or Unified Contact Center Express version
    Access the admin web interface of Cisco Unified Intelligence Center or Unified Contact Center Express and navigate to the About or System Information page to view the software version. Alternatively, use the CLI and run 'show version' or 'utils system version' command if available.
    Affected if The displayed version matches 8.5.4, 9.0(2), 9.1(1) for CUIC, or 10.0(1), 10.5(1), 10.6(1), 11.0(1) for Unified Contact Center Express.
  2. Verify the web interface is accessible
    Confirm that the Cisco Unified Intelligence Center or Unified Contact Center Express web interface is reachable on the network by attempting to access the login page via HTTPS or HTTP.
    Affected if The web interface is exposed and reachable, making the XSS vulnerability potentially exploitable.
  3. Check for applied security patch CSCuy75020 or CSCuy81652
    In the Cisco admin interface, look for installed software updates or patches. In the CLI, check the patch status using 'show patch status' or 'utils cup patch list' if applicable. Alternatively, review the system logs for evidence that the security patch has been installed.
    Affected if No patch for CSCuy75020 or CSCuy81652 is installed, meaning the security update addressing this XSS vulnerability has not been applied.
  4. Review URL parameter handling
    If you have access to test the application, craft a test URL with a benign script payload in a parameter (for example, ?param=<script>alert('test')</script>) and observe whether the script is reflected back in the response without sanitization. In a production environment, review HTTP access logs for unusual URL patterns with script tags.
    Affected if URL parameters containing HTML or script tags are reflected in the response without proper encoding or validation.

The environment is affected if Cisco Unified Intelligence Center version 8.5.4, 9.0(2), or 9.1(1) OR Cisco Unified Contact Center Express version 10.0(1), 10.5(1), 10.6(1), or 11.0(1) is installed, the web interface is accessible, and security patch CSCuy75020/CSCuy81652 has not been applied.

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 security patch for CSCuy75020/CSCuy81652 to affected CUIC versions 8.5.4 through 9.1(1) and corresponding Unified Contact Center Express versions 10.0(1) through 11.0(1). As a compensating control, implement Content Security Policy (CSP) headers and validate URL parameters server-side before rendering.

Fix this in Unified Contact Center Express Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6425 — 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-2016-6425 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