CVE-2026-20116
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 Finesse, Cisco Packaged Contact Center Enterprise (Packaged CCE), Cisco Unified Contact Center Enterprise (Unified CCE), Cisco Unified Contact Center Express (Unified CCX), and Cisco Unified Intelligence Center 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 · moderate confidenceThis is a stored XSS vulnerability affecting Cisco's contact center management interfaces (Finesse, Packaged CCE, Unified CCE, Unified CCX, and Unified Intelligence Center). The web interface insufficiently validates user-supplied input, allowing an unauthenticated remote attacker to inject malicious script code into specific pages. Successful exploitation enables arbitrary script execution in the user's browser context 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.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify deployed Cisco contact center productsInventory your environment for installed instances of Finesse, Packaged CCE, Unified CCE, Unified CCX, or Unified Intelligence Center. Check installed software listings, services, or running processes for these product names.Affected if Any of these products are present in the environment and the version is unpatched against CVE-2026-20116
-
Locate the web management interfaceIdentify the URL and port used to access the Finesse, Packaged CCE, Unified CCE, Unified CCX, or Unified Intelligence Center web interfaces (typically HTTPS on ports 443, 8443, or product-specific ports). Note whether it is externally accessible or internal only.Affected if The web interface is accessible (even internally) and the installed product version lacks the CVE-2026-20116 patch
-
Examine stored data for malicious script payloadsReview application logs, database tables (particularly user input fields, configuration entries, or contact/agent records), or administrative console pages for unusual script tags, HTML elements, or encoded JavaScript payloads such as <script>, javascript:, or event handlers like onload/onerror.Affected if Malicious script code is found stored in the application database, logs, or displayed in the web interface itself
-
Verify the installed product versionLog into the web interface or CLI of each affected product and locate the version information (usually in About, System Information, or Help sections). Compare against any vendor-released patch versions for CVE-2026-20116.Affected if The installed version matches an unpatched release of Finesse, Packaged CCE, Unified CCE, Unified CCX, or Unified Intelligence Center
The environment is affected if any Cisco contact center product (Finesse, Packaged CCE, Unified CCE, Unified CCX, or Unified Intelligence Center) is running with an unpatched version and has its web interface accessible.
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 the affected products when released. As a temporary measure, implement a WAF rule to filter malicious input patterns and restrict web interface access to trusted users until patching is complete.
- 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-2026-20116 — 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-20116 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