CVE-2023-20205
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 confidenceStored cross-site scripting (XSS) vulnerabilities in Cisco Prime Infrastructure and Cisco EPNM web-based management interfaces due to insufficient validation of user-supplied input. An authenticated attacker can inject malicious HTML/script content that persists on the server and executes in the context of other users' browsers when they view the affected pages.
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< 7.1< 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 installed product and versionAccess the web-based management interface and locate the version information, typically found in the About or Help section of the UI. Alternatively, check the installed software package on the server system.Affected if The product is Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager and the displayed version falls below 3.10.4 for Prime Infrastructure or below 7.1 for EPNM.
-
Confirm web management interface is enabledVerify that the web-based management interface is accessible and running. This is typically accessible on port 443 or 8080 for HTTPS/HTTP connections to the management IP.Affected if The web interface is exposed and accessible to users.
-
Check authentication configurationReview whether local user accounts or external authentication (such as LDAP or RADIUS) is configured for the management interface access.Affected if User authentication is enabled and configured, as the vulnerability requires an authenticated attacker to inject malicious content.
You are affected if you are running Cisco Prime Infrastructure below version 3.10.1 or Cisco Evolved Programmable Network Manager below version 7.1, and the web-based management interface is accessible and allows user authentication.
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 Cisco's security patches for CVE-2023-20205 when available; implement robust input validation and output encoding for all user-supplied data rendered in the web interface.
Cisco Prime Infrastructure: upgrade to 3.10.4 or later; Cisco Evolved Programmable Network Manager: upgrade to 7.1 or later
- 1. Identify which product is in use: Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager (EPNM).
- 2. Determine the current installed version from the web-based management interface or system documentation.
- 3. For Cisco Prime Infrastructure: Plan upgrade to version 3.10.4 or later.
- 4. For Cisco Evolved Programmable Network Manager: Plan upgrade to version 7.1 or later.
- 5. Review Cisco release notes and upgrade documentation for your specific product version.
- 6. Ensure valid credentials are available for the web-based management interface (required for the upgrade process).
- 7. Perform a backup of the current configuration before initiating the upgrade.
- 8. Execute the upgrade following Cisco's documented upgrade procedure for the specific product.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20205 — 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-20205 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