Unified Contact Center ExpressApplication · Cisco
CVE-2026-20117
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 Contact Center Express (Unified CCX) could allow an unauthenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the interface. This vulnerability exists because the web-based management interface of an affected system does not sufficiently validate user-supplied input. An attacker could exploit this vulnerability by injecting malicious code into specific pages of the interface. 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 confidenceThis is a stored XSS vulnerability in Cisco Unified CCX's web-based management interface where the application fails to properly sanitize user-supplied input before rendering it in the page. An unauthenticated attacker can inject malicious JavaScript into specific pages, which will execute in the victim's browser when they access those pages, allowing session hijacking or data theft.
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
<= 15.0\(1\)ES01CVSS 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.
-
Confirm Cisco Unified CCX installationLocate and identify the Cisco Unified Contact Center Express product in your environment. This is typically found on dedicated Voice/Contact Center infrastructure. Check your asset inventory or run appropriate discovery commands for Cisco collaboration products.Affected if The product is not present in your environment.
-
Check installed version numberAccess the web-based management interface or use CLI commands to retrieve the exact version of Cisco Unified CCX installed. Compare the version to the affected range: any version up to and including 15.0(1)ES01.Affected if Your installed version is 15.0(1)ES01 or any earlier version.
-
Verify web management interface is enabledConfirm that the web-based management interface (typically accessed via HTTPS on ports 8443 or 443) is currently enabled and running on your Cisco Unified CCX system.Affected if The web management interface is disabled and not accessible.
-
Assess network accessibility of the management interfaceDetermine if the management interface is exposed to untrusted networks. Check firewall rules, ACLs, or network segmentation configurations that control access to the web management port.Affected if The management interface is accessible only from trusted/admin networks (internal only) and not directly exposed to the internet or untrusted users.
You are affected if Cisco Unified CCX is installed with version 15.0(1)ES01 or earlier AND the web management interface is network-accessible to untrusted users.
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 the vendor patch when released. In the interim, restrict network access to the management interface to trusted networks only, and consider deploying a WAF with XSS filtering rules.
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
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 locallyCheck whether your project pulls in CVE-2026-20117 — 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-2026-20117 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