dbcve.org
Prime Service CatalogApplication · Cisco

CVE-2016-1462

MEDIUM · 6.1 CVSS v3.0 Published 2016-07-28
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
Cross-site scripting (XSS) vulnerability in the web-based management interface in Cisco Prime Service Catalog (PSC) 11.0 allows remote attackers to inject arbitrary web script or HTML via a crafted value, aka Bug ID CSCuz63795.

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 stored Cross-Site Scripting (XSS) vulnerability exists in the web-based management interface of Cisco Prime Service Catalog 11.0. Remote attackers can inject arbitrary web script or HTML by submitting a crafted value through the interface, which is then stored and executed when other users view the affected content.

MitigationApply the vendor patch for CSCuz63795. Until then, implement input validation and output encoding for all user-supplied values in the management interface, and consider disabling the affected web interface or restricting access to trusted IP addresses.

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 Service CatalogApplication
Affected:= 11.0_base

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.0/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 Cisco Prime Service Catalog version
    Locate the installed version of Cisco Prime Service Catalog in the system. This is typically found in the software inventory, about page, or installation directory. Common methods include checking the application's help menu, the installation logs, or running: 'show version' if CLI access is available, or reviewing the /opt directory for the installed package.
    Affected if The installed version is exactly 11.0_base (version 11.0)
  2. Confirm web management interface is enabled
    Determine whether the web-based management interface for Cisco Prime Service Catalog is currently active and accessible. Check if the HTTP/HTTPS service for port 8080, 8443, or the default web ports are listening and responding.
    Affected if The web-based management interface is enabled and accessible on the network
  3. Verify admin or user access to the management interface
    Determine if standard user accounts or administrator accounts have access to submit values through the web management interface. Log in to the interface and navigate to forms, configuration pages, or input fields where user-supplied data can be stored.
    Affected if User or admin accounts can submit stored content through the web interface
  4. Review stored content for potential XSS payloads
    Inspect stored values in the management interface database or application. Check user profile fields, configuration parameters, service request forms, or any area where submitted data is persisted and displayed to other users. Look for unsanitized HTML or script tags.
    Affected if Stored content in the management interface contains unsanitized user input that could execute as JavaScript

You are affected if Cisco Prime Service Catalog version 11.0_base is installed and the web-based management interface is enabled, as this combination allows the stored XSS vulnerability to be exploited.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CSCuz63795. Until then, implement input validation and output encoding for all user-supplied values in the management interface, and consider disabling the affected web interface or restricting access to trusted IP addresses.

Fix this in Prime Service Catalog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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