dbcve.org
Webex Contact CenterApplication · Cisco

CVE-2026-20170

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-15
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 Desktop Agent functionality of Cisco Webex Contact Center could have allowed an unauthenticated, remote attacker to conduct cross-site scripting attacks. Cisco has addressed this vulnerability in the Cisco Webex Contact Center service, and no customer action is needed. This vulnerability existed because HTML and script content was not properly handled. Prior to this vulnerability being addressed, an attacker could have exploited this vulnerability by persuading a user to follow a malicious link. A successful exploit could have allowed the attacker to steal sensitive information from the browser, including authentication and session 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

A reflected cross-site scripting (XSS) vulnerability in the Desktop Agent functionality of Cisco Webex Contact Center allowed unauthenticated remote attackers to inject malicious HTML/script content via specially crafted URLs. Successful exploitation could have enabled attackers to steal sensitive browser data including authentication credentials and session tokens.

MitigationNo customer action required as Cisco has already addressed this vulnerability in the service. Users should remain vigilant about clicking untrusted links as a general security practice.

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
Webex Contact CenterApplication
Affected:all versions

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. Confirm Cisco Webex Contact Center deployment
    Inventory your environment for installations of Cisco Webex Contact Center, particularly the Desktop Agent component. Check for installed software named 'Cisco Webex Contact Center' or 'Webex CC' on systems.
    Affected if Cisco Webex Contact Center Desktop Agent software is present in the environment
  2. Identify Desktop Agent web access points
    Locate URLs or endpoints used to access the Desktop Agent functionality. This is typically a web-based interface used by contact center agents. Check your internal documentation or network traffic logs for URLs containing paths related to Desktop Agent, agent login, or contact center portals.
    Affected if Desktop Agent is accessible via web browser at any URL within your environment
  3. Verify product version
    Check the installed version of Cisco Webex Contact Center Desktop Agent. Access the agent desktop application or its about/settings panel, or query the software inventory. Compare against the affected version range.
    Affected if Any version of Cisco Webex Contact Center Desktop Agent is installed (vulnerable by design since all versions are affected)
  4. Review for exploitation indicators
    Examine web server access logs, proxy logs, or security appliance logs for incoming requests to Desktop Agent URLs containing suspicious patterns such as script tags, javascript:, or unusual URL parameters that might indicate XSS probing. Look for requests with patterns like <script>, %3Cscript%3E, onerror=, or similar XSS vectors in query strings.
    Affected if Logs show crafted requests with XSS payload patterns targeting Desktop Agent endpoints

Organizations with Cisco Webex Contact Center Desktop Agent deployed and accessible via web are affected by this reflected XSS vulnerability, though Cisco has already addressed it in the service.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

No customer action required as Cisco has already addressed this vulnerability in the service. Users should remain vigilant about clicking untrusted links as a general security practice.

Recommended fix High confidence
  1. No customer action is required. Cisco has addressed this vulnerability server-side in the Cisco Webex Contact Center service. The fix was applied automatically to the cloud infrastructure.

Generated from the published advisory — verify against the referenced sources before acting.

We can implement and validate the mitigation, then track the permanent fix — typical engagement from $1,600. Get help mitigating

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2026-20170 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