Unified Communications ManagerApplication · Cisco

CVE-2019-12715

MEDIUM · 6.1 CVSS v3.1 Published 2019-10-02
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 interface of Cisco Unified Communications Manager and Cisco Unified Communications Manager Session Management Edition (SME) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based interface of the affected software. The vulnerability is due to insufficient validation of user-supplied input by the web-based interface of the affected software. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive browser-based information.

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

Cross-site scripting (XSS) vulnerability in Cisco Unified Communications Manager and Cisco Unified Communications Manager Session Management Edition web interface allows unauthenticated remote attackers to inject malicious script code via insufficiently validated user-supplied input, potentially enabling execution in the context of the affected interface or theft of sensitive browser-based information.

MitigationApply the vendor patch from Cisco for CVE-2019-12715. Users should be warned about clicking untrusted links as a defense-in-depth measure until the patch is deployed.

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:= 10.5\(2.10000.5\)= 11.5\(1.10000.6\)= 12.0\(1.10000.10\)= 12.5\(1.10000.22\)

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

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

  1. Identify installed Cisco UCM version
    Access the Cisco UCM admin interface and navigate to About > Licensing, or log into the CLI and run the command 'show version' or 'utils system version'. Record the exact build number displayed.
    Affected if the displayed build number matches exactly 10.5(2.10000.5), 11.5(1.10000.6), 12.0(1.10000.10), or 12.5(1.10000.22)
  2. Confirm web interface is accessible
    Attempt to reach the Cisco UCM web interface by accessing the primary hostname or IP address over HTTPS (typically port 8443 or 443). Verify the login page loads successfully.
    Affected if the web interface responds and displays a login page, indicating it is exposed
  3. Cross-reference version against CVE-affected builds
    Compare the recorded build number from step 1 against the four vulnerable builds listed in the CVE: 10.5(2.10000.5), 11.5(1.10000.6), 12.0(1.10000.10), 12.5(1.10000.22).
    Affected if the installed version exactly matches one of these four specific builds

You are affected if your Cisco Unified Communications Manager version matches one of the four specific builds AND the web interface is accessible to network users.

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 vendor patch from Cisco for CVE-2019-12715. Users should be warned about clicking untrusted links as a defense-in-depth measure until the patch is deployed.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12715 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-12715 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