Unified Communications ManagerApplication · Cisco
CVE-2022-20800
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-based management interface of Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), and Cisco Unity Connection could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. This vulnerability exists because the web-based management interface does not properly validate user-supplied input. 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 confidenceCross-site scripting (XSS) vulnerability in Cisco Unified Communications Manager web-based management interface. The interface fails to properly validate user-supplied input, allowing an unauthenticated remote attacker to inject malicious script code via a crafted link. Successful exploitation enables arbitrary JavaScript execution in the context of the affected interface or access to sensitive browser-based information.
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
>= 11.5\(1\), < 14su2
Unified Communications Manager Im And Presence ServiceApplication
>= 11.5\(1\), < 12.5\(1\)su5
Unity ConnectionApplication
>= 11.5\(1\), < 14su2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the affected productAccess the web-based management interface or use the command line interface (CLI) to determine which Cisco product is deployed: Cisco Unified Communications Manager (CUCM), Cisco Unified Communications Manager IM and Presence Service, or Cisco Unity Connection. Note the specific product name as it appears in your environment.Affected if The deployed product is one of CUCM, CUCM IM and Presence Service, or Unity Connection.
-
Check the installed versionIn the web-based management interface, navigate to the About page or use the CLI command 'show version' to obtain the exact installed version number. Compare this version against the affected ranges: CUCM and Unity Connection versions 11.5(1) through versions less than 14su2; CUCM IM and Presence Service versions 11.5(1) through versions less than 12.5(1)su5.Affected if The installed version falls within 11.5(1) up to but not including 14su2 (for CUCM or Unity Connection) or 12.5(1)su5 (for IM and Presence Service).
-
Verify the web management interface is accessibleConfirm that the web-based management interface is currently running and reachable on the network. Attempt to access the login page via HTTP/HTTPS from a browser or using a tool like curl from the command line.Affected if The web-based management interface is accessible over the network and responds to requests.
-
Assess network exposureDetermine if the management interface is exposed to untrusted networks. Check firewall rules, ACLs, or reverse proxy configurations to identify whether the interface is accessible from outside trusted internal networks or the internet.Affected if The web interface is accessible from untrusted networks or the internet without proper network-level access controls.
If the installed product version is within the affected ranges (11.5(1) to <14su2 for CUCM/Unity Connection, or 11.5(1) to <12.5(1)su5 for IM and Presence Service) AND the web-based management interface is accessible, the environment is potentially affected by this XSS vulnerability.
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.
dbcve · scoped12.514su2
Apply the relevant Cisco security patches for CVE-2022-20800 when available. Until patched, consider disabling the web-based management interface or restricting access to trusted networks, and educate users about not clicking untrusted links.
Unified CM: 14su2 | Unified CM IM&P: 12.5(1)su5 | Unity Connection: 14su2
- 1. Identify the exact deployed product and version (Unified CM, Unified CM IM&P, or Unity Connection)
- 2. For Unified Communications Manager: Upgrade to version 14su2 (or later)
- 3. For Unified Communications Manager IM & Presence Service: Upgrade to version 12.5(1)su5 (or later)
- 4. For Unity Connection: Upgrade to version 14su2 (or later)
- 5. After upgrade, verify the web-based management interface is accessible and functional
- 6. Test that the XSS vulnerability is no longer present by attempting to inject script tags in input fields
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20800 — 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-2022-20800 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