dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2019-12713

MEDIUM · 6.1 CVSS v3.1 Published 2019-10-02
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 web-based management interface of Cisco Prime Infrastructure could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based management interface of the affected software. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of the affected software. 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.

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

Reflected cross-site scripting (XSS) vulnerability in Cisco Prime Infrastructure's web-based management interface allows unauthenticated remote attackers to inject malicious script code via crafted URLs. The flaw stems from insufficient validation of user-supplied input in the web interface.

MitigationApply the relevant Cisco security patch for CVE-2019-12713. Users should avoid clicking untrusted links to the management interface until the patch is applied.

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 InfrastructureApplication
Affected:= 3.5

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 Prime Infrastructure is installed
    Locate the Cisco Prime Infrastructure installation. On Linux, check for /opt/cpi or look for the 'Prime Infrastructure' service using 'ps aux | grep -i prime' or 'systemctl list-units | grep -i prime'. On Windows, check Services for 'Cisco Prime Infrastructure' or look in Program Files.
    Affected if The product is not installed or the service is not running.
  2. Identify the installed version
    Access the web management interface and log in, then navigate to Administration > Software Updates > Software Catalog, or check the version via CLI: 'show version' from the Prime Infrastructure console. Alternatively, check /opt/CSU-lite/version.txt or the installation directory for a version file.
    Affected if The version is exactly 3.5 (CPE 3.5.x).
  3. Verify the web interface is externally accessible
    Check network exposure of the web interface by reviewing firewall rules or performing an external port scan (typically ports 443, 80, 8080, 8443). Confirm whether the management interface is reachable from untrusted networks.
    Affected if The web interface is exposed to untrusted networks or the internet.
  4. Review URL parameters for input validation issues
    If the web interface is accessible, capture a sample of legitimate URLs from the interface (e.g., navigation links, search parameters). Inspect whether user-supplied input in URL parameters is reflected back without proper encoding. Look for parameters in the query string that accept user input.
    Affected if User-supplied input in URLs is reflected unescaped in responses.

You are affected if Cisco Prime Infrastructure version 3.5 is running with its web-based management interface accessible, as the reflected XSS flaw requires no authentication and exploits insufficient input validation in the web interface.

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 relevant Cisco security patch for CVE-2019-12713. Users should avoid clicking untrusted links to the management interface until the patch is applied.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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