Evolved Programmable Network ManagerApplication · Cisco
CVE-2023-20201
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 an authenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface on an affected device. These vulnerabilities are due to insufficient validation of user-supplied input. An attacker could exploit these vulnerabilities by persuading a user of an affected interface to view a page containing malicious HTML or script content. 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. To exploit these vulnerabilities, the attacker must have valid credentials to access the web-based management interface of the affected device.
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 confidenceMultiple stored XSS vulnerabilities in Cisco Prime Infrastructure and EPNM web management interfaces due to insufficient validation of user-supplied input. An authenticated attacker can inject malicious HTML/script content that executes in the context of the affected interface when viewed by other users.
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
Evolved Programmable Network ManagerApplication
< 7.1
Prime InfrastructureApplication
< 3.10.4CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Cisco productAccess the web management interface and look for the product name in the login page, header, or help/about section. Alternatively, check the URL path (e.g., /epi for EPNM, /PI for Prime Infrastructure) or review system documentation.Affected if The product is Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager (EPNM)
-
Determine the installed versionIn the web interface, navigate to Help > About or Administration > Software Updates to view the version number. From CLI, run 'show version' or 'admin# show inventory' depending on access.Affected if The version is below 3.10.4 for Prime Infrastructure or below 7.1 for EPNM
-
Verify web management interface is enabledCheck if the web-based management interface (HTTP/HTTPS on ports 80/443 or custom ports) is accessible and responding. Confirm the /PI or /epi endpoints are reachable.Affected if The web management interface is exposed and accessible
-
Check for untrusted user accountsReview user accounts in Administration > User Management or AAA configuration. Look for any unexpected or unauthorized user accounts with administrative or elevated privileges.Affected if There are untrusted or unauthorized user accounts with access to the management interface
-
Inspect for suspicious stored contentNavigate to configuration pages, device groups, templates, or any user-created content areas. Look for unexpected HTML tags, script elements, or encoded payloads in fields that accept user input.Affected if Malicious scripts have been injected into stored configuration fields
A user is affected if they run Cisco Prime Infrastructure below version 3.10.1 or EPNM below version 7.1 and have the web management interface accessible to authenticated users.
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.47.1
Apply vendor-provided patches for CVE-2023-20201. Until patches are available, restrict web management interface access to trusted users only and monitor for suspicious activity.
EPNM 7.1+ or Prime Infrastructure 3.10.4+
- Identify which Cisco product is affected: Prime Infrastructure or Evolved Programmable Network Manager (EPNM)
- For Prime Infrastructure: Check current version - if below 3.10.4, plan upgrade to version 3.10.4 or later
- For Evolved Programmable Network Manager (EPNM): Check current version - if below 7.1, plan upgrade to version 7.1 or later
- Review release notes for the target version to understand any required migration steps or prerequisites
- Schedule maintenance window for upgrade implementation
- Backup current configuration before performing upgrade
- Upgrade to the fixed version (3.10.4+ for Prime Infrastructure, 7.1+ for EPNM)
- After upgrade, verify the web interface is accessible and functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Evolved Programmable Network Manager
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20201 — 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-20201 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