dbcve.org
Prime Collaboration DeploymentApplication · Cisco

CVE-2023-20060

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 14su3 or later.
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 web-based management interface of Cisco Prime Collaboration Deployment could allow an unauthenticated, remote attacker to conduct a cross-site scripting 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. Cisco plans to release software updates that address this vulnerability. There are no workarounds that address this vulnerability.

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

This is a reflected cross-site scripting (XSS) vulnerability in Cisco Prime Collaboration Deployment's web-based management interface. The interface fails to properly validate user-supplied input, allowing attackers to inject malicious scripts through crafted URLs that execute in the context of authenticated users' browser sessions.

MitigationApply the Cisco vendor patch when released. In the interim, exercise caution with links and consider network segmentation to limit exposure to the management interface.

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
Prime Collaboration DeploymentApplication
Affected:< 14su3

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. Identify the installed product
    Access the web management interface or check system inventory to confirm the product name is Cisco Prime Collaboration Deployment
    Affected if The product is not Cisco Prime Collaboration Deployment
  2. Check the installed version
    Locate the version information in the web interface (typically under Help > About) or via CLI command 'show version' if available, then compare against 14su3
    Affected if The installed version is lower than 14su3 (e.g., 14su1, 14su2, or any 14.x version prior to 14su3)
  3. Confirm web management interface is enabled
    Verify the web-based management interface is active and accessible - check if HTTPS/HTTP ports for the management interface are listening
    Affected if The web management interface is enabled and exposed
  4. Assess interface accessibility
    Determine if the management interface is reachable from network segments beyond localhost or trusted admin networks
    Affected if The interface is accessible from untrusted networks or does not require VPN/tunnel for access

The environment is affected if Cisco Prime Collaboration Deployment is running a version lower than 14su3 and the web-based management interface is enabled and accessible.

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
Upgrade available Upgrade to 14su3 or later
Fixed in 14su3
Interim mitigation

Apply the Cisco vendor patch when released. In the interim, exercise caution with links and consider network segmentation to limit exposure to the management interface.

Recommended fix Moderate confidence

14su3 (or later release)

  1. 1. Back up the current Cisco Prime Collaboration Deployment configuration and data.
  2. 2. Verify the current installed version is below 14su3 using the web-based management interface or CLI.
  3. 3. Obtain the Cisco Prime Collaboration Deployment 14su3 or later software update from the Cisco software download center (requires valid Cisco service contract).
  4. 4. Follow Cisco's standard upgrade procedure for Prime Collaboration Deployment: access the Administration > Software Updates section in the web interface, or use the CLI upgrade command.
  5. 5. Upload the 14su3 (or later) software image and initiate the upgrade.
  6. 6. Verify the upgrade completed successfully and the new version 14su3 is running.
  7. 7. Confirm the XSS vulnerability is remediated by testing that user-supplied input in the web interface is properly sanitized.
Caveat Standard Cisco maintenance update - review release notes for any configuration or feature changes

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

Fix this in Prime Collaboration Deployment Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-20060 — 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-2023-20060 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