dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2023-20127

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-05
Fix available
A fix is available. Upgrade to 3.10.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Multiple vulnerabilities in the web-based management interface of Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager (EPNM) could allow a remote attacker to obtain privileged information and conduct cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks. For more information about these vulnerabilities, see the Details section of this advisory.

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 confidence

Multiple vulnerabilities exist in the web-based management interface of Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager (EPNM). These include an information disclosure vulnerability allowing privileged information access, cross-site scripting (XSS) vulnerabilities, and cross-site request forgery (CSRF) vulnerabilities. A remote attacker could exploit these through the web interface without authentication in some cases.

MitigationApply Cisco security patches/updates for Prime Infrastructure and EPNM when available. Restrict network access to management interfaces, implement CSRF tokens, and validate/sanitize user inputs to mitigate XSS and CSRF vectors.

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.7>= 3.10, < 3.10.2= 3.8= 3.8.1= 3.9= 3.9.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if Cisco Prime Infrastructure is installed
    Check for the product by reviewing installed software packages, looking for 'Cisco Prime Infrastructure' in system inventory, or accessing the web management interface at the expected URL (typically https://<host>/PI)
    Affected if The product is present on the system
  2. Determine the installed version of Cisco Prime Infrastructure
    Log into the web-based management interface and navigate to the About or Version page, or use the CLI command 'show version' if SSH access is available to the appliance
    Affected if The version cannot be determined or does not match the expected version numbering scheme
  3. Compare your version against the affected ranges
    Review the installed version number against these affected versions: all versions <= 3.7, versions 3.8, 3.8.1, 3.9, 3.9.1, and versions >= 3.10 but < 3.10.2
    Affected if Your installed version falls within any of these ranges: <= 3.7, 3.8, 3.8.1, 3.9, 3.9.1, or 3.10 through 3.10.1
  4. Verify if the web-based management interface is accessible
    Attempt to access the Prime Infrastructure web interface over HTTP/HTTPS from a network location, or check firewall rules and listener configurations on the host
    Affected if The web management interface is reachable from network segments beyond the trusted management network
  5. Check for indicators of exploitation
    Review web server access logs for unusual patterns, unauthorized user accounts, or unexpected administrative actions in audit logs
    Affected if Suspicious activity patterns are found in logs or unauthorized configuration changes are detected

You are affected if Cisco Prime Infrastructure is installed and the version falls within <= 3.7, 3.8, 3.8.1, 3.9, 3.9.1, or >= 3.10 but < 3.10.2, especially if the web interface is network-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.

From vendor data
Upgrade available Upgrade to 3.10.2 or later
Fixed in 3.10.2
Interim mitigation

Apply Cisco security patches/updates for Prime Infrastructure and EPNM when available. Restrict network access to management interfaces, implement CSRF tokens, and validate/sanitize user inputs to mitigate XSS and CSRF vectors.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

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