Unified Communications ManagerApplication · Cisco
CVE-2018-0328
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 · uneditedA vulnerability in the web framework of Cisco Unified Communications Manager and Cisco Unified Presence could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web interface of an affected system. The vulnerability is due to insufficient input validation of certain parameters that are passed to the affected software via the HTTP GET and HTTP POST methods. An attacker who can convince a user to follow an attacker-supplied link could execute arbitrary script or HTML code in the user's browser in the context of an affected site. Cisco Bug IDs: CSCvg89116.
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 Cisco Unified Communications Manager and Cisco Unified Presence web framework. Insufficient input validation of HTTP GET and POST parameters allows unauthenticated remote attackers to inject malicious script/HTML via attacker-supplied links, executing in user browsers within the affected site's context.
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
= 10.5\(2.10000.5\)= 11.0\(1.10000.10\)= 11.5\(1.10000.6\)= 12.0\(1.10000.10\)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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed productAccess the Cisco Unified Communications Manager administration interface and navigate to the About page, or use the CLI command 'show version' to determine if the system is running Cisco Unified Communications Manager or Cisco Unified PresenceAffected if The system is running either Cisco Unified Communications Manager or Cisco Unified Presence
-
Determine the exact version buildLocate the full version string in the About page or CLI output - look for the specific build number in the format such as 10.5(2.10000.5), 11.0(1.10000.10), 11.5(1.10000.6), or 12.0(1.10000.10)Affected if The installed version exactly matches 10.5(2.10000.5), 11.0(1.10000.10), 11.5(1.10000.6), or 12.0(1.10000.10)
-
Verify the web framework is accessibleConfirm that the Cisco Unified Communications Manager or Unified Presence web interface is reachable over HTTP/HTTPS from network locations where users could click attacker-supplied linksAffected if The web interface is exposed and accessible to users or attackers who could be tricked into clicking malicious links
The environment is affected if the installed version of Cisco Unified Communications Manager or Unified Presence exactly matches one of the four vulnerable builds and the web framework is accessible to users who could click attacker-supplied links.
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 Cisco Unified Communications Manager and Unified Presence. Additionally, implement output encoding and input validation for all user-supplied parameters in web interfaces to prevent XSS attacks.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0328 — 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-0328 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