Prime InfrastructureApplication · Cisco

CVE-2023-20129

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-05
Fix available
A fix is available. Upgrade to 3.10.2 / 5.0.2.5 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 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.

MitigationApply Cisco's security updates for this vulnerability; until patched, restrict network access to management interfaces and implement input validation controls.

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
Evolved Programmable Network ManagerApplication
Affected:< 5.0.2.5>= 5.1, < 5.1.4.2>= 6.0, < 6.0.2.1>= 6.1, < 6.1.1.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 deployed
    Log into the device and run 'show version' or access the web UI login page to confirm the product name
    Affected if The product is Cisco Prime Infrastructure
  2. Check Cisco Prime Infrastructure version
    From the web UI, go to Home > Dashboard or use 'show version' CLI command to retrieve the installed version number
    Affected if The version is <= 3.7, 3.8, 3.8.1, 3.9, 3.9.1, or >= 3.10 but < 3.10.2
  3. Identify if Cisco Evolved Programmable Network Manager is deployed
    Log into the device and run 'show version' or access the web UI login page to confirm the product name is Cisco EPNM
    Affected if The product is Cisco EPNM
  4. Check Cisco EPNM version
    From the web UI, go to Administration > System > Software Version or use 'show version' CLI command to retrieve the installed version number
    Affected 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
  5. Verify web management interface is accessible
    Confirm the web-based management interface (HTTP/HTTPS on port 443 or 8080) is listening and reachable on the device
    Affected if The web management interface is exposed and the version is in the affected range

You are affected if either Cisco Prime Infrastructure or Cisco EPNM is running and the installed version matches the affected version ranges, with the web management interface enabled.

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 / 5.0.2.5 / 5.1.4.2 or later
Fixed in 3.10.25.0.2.55.1.4.2
Interim mitigation

Apply Cisco's security updates for this vulnerability; until patched, restrict network access to management interfaces and implement input validation controls.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-20129 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