Prime InfrastructureApplication · Cisco
CVE-2023-20130
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 · uneditedMultiple 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 confidenceMultiple vulnerabilities in the web-based management interfaces of Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager (EPNM) allow remote attackers to obtain privileged information and conduct cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks. These are application-level flaws in the web UI that bypass security boundaries.
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
<= 3.7>= 3.10, < 3.10.2= 3.8= 3.8.1= 3.9= 3.9.1
Evolved Programmable Network ManagerApplication
< 5.0.2.5>= 5.1, < 5.1.4.2>= 6.0, < 6.0.2.1>= 6.1, < 6.1.1.1CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Cisco Prime Infrastructure or EPNM is installedReview running processes or installed applications on the system for 'Cisco Prime Infrastructure', 'Cisco PI', 'EPNM', or 'Evolved Programmable Network Manager' processes or servicesAffected if Either product is present on the system
-
Determine the installed version of Cisco Prime InfrastructureAccess the web management interface and navigate to the About or Version page, or run the command 'show version' in the CLI if availableAffected if The version is <= 3.7, = 3.8, = 3.8.1, = 3.9, = 3.9.1, = 3.9.1, >= 3.10 but < 3.10.2
-
Determine the installed version of Cisco EPNMAccess the web management interface and navigate to the About or Version page, or run the command 'show version' in the CLI if availableAffected if The version is < 5.0.2.5, >= 5.1 but < 5.1.4.2, >= 6.0 but < 6.0.2.1, or >= 6.1 but < 6.1.1.1
-
Check if the web management interface is network-accessibleVerify if TCP ports 443, 8080, or the configured management HTTP/HTTPS ports are exposed to untrusted networks or the internetAffected if The web UI is accessible from untrusted networks without ACL restrictions
-
Review admin audit logs for suspicious activityExamine Cisco PI/EPNM admin logs for unexpected account creation, privilege escalation, or unusual configuration changesAffected if Unexplained administrative actions or new user accounts are present in the logs
The environment is affected if either Cisco Prime Infrastructure or EPNM is running a version within the affected ranges AND the web management interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.10.25.0.2.55.1.4.2
Apply Cisco security patches when available; restrict network access to management interfaces using ACLs or VPN; implement WAF rules for XSS/CSRF vectors; monitor for anomalous administrative actions.
Prime Infrastructure: 3.10.2; EPNM: 5.0.2.5, 5.1.4.2, 6.0.2.1, or 6.1.1.1 (depending on current branch)
- 1. Identify the current installed version of Cisco Prime Infrastructure (PI) or Evolved Programmable Network Manager (EPNM)
- 2. For Prime Infrastructure users: If running version 3.10.x, upgrade to version 3.10.2 or later. If running 3.8, 3.8.1, or 3.7/earlier, plan migration to 3.10.2
- 3. For EPNM users: Determine which version range applies - upgrade to 5.0.2.5 or later (if on 4.x), 5.1.4.2 or later (if on 5.1.x), 6.0.2.1 or later (if on 6.0.x), or 6.1.1.1 or later (if on 6.1.x)
- 4. Before upgrading, backup the current configuration and database
- 5. Schedule maintenance window as upgrade may require downtime
- 6. Follow Cisco's standard upgrade procedure for the specific product version
- 7. After upgrade, verify the web interface is accessible and the version number reflects the upgrade
- 8. Confirm the vulnerabilities are remediated by reviewing the Cisco security advisory
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prime Infrastructure
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-20130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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