Evolved Programmable Network ManagerApplication · Cisco
CVE-2025-20270
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 · uneditedA vulnerability in the web-based management interface of Cisco Evolved Programmable Network Manager (EPNM) and Cisco Prime Infrastructure could allow an authenticated, remote attacker to obtain sensitive information from an affected system. This vulnerability is due to improper validation of requests to API endpoints. An attacker could exploit this vulnerability by sending a valid request to a specific API endpoint within the affected system. A successful exploit could allow a low-privileged user to view sensitive configuration information on the affected system that should be restricted. To exploit this vulnerability, an attacker must have access as a low-privileged user.
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 confidenceAn information disclosure vulnerability in Cisco Evolved Programmable Network Manager (EPNM) and Cisco Prime Infrastructure allows authenticated low-privileged users to access sensitive configuration information through API endpoints due to improper request validation. The attacker exploits this by sending valid requests to specific API endpoints that should be restricted.
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.0>= 8.0.0, < 8.0.1>= 8.1.0, < 8.1.2
Prime InfrastructureApplication
<= 3.9>= 3.10, <= 3.10.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed product and versionDetermine whether Cisco Evolved Programmable Network Manager (EPNM) or Cisco Prime Infrastructure is deployed. Locate the version number from the product web UI (typically in About or Diagnostics sections) or CLI interface.Affected if Running EPNM versions <= 7.1.0, >= 8.0.0 and < 8.0.1, or >= 8.1.0 and < 8.1.2; OR Prime Infrastructure versions <= 3.9, or >= 3.10 and <= 3.10.6
-
Confirm API access is enabledVerify that the REST API functionality is enabled in the product. Check API-related settings in the administration or system configuration pages, or review if TCP ports for API access are listening.Affected if API endpoints are accessible and the product version is in the affected ranges listed above
-
Review low-privileged user accountsExamine the user directory to identify accounts with read-only or limited privileges. These are the account types that could exploit this vulnerability.Affected if Low-privileged (non-admin) user accounts exist and the product version is vulnerable
-
Inspect API access logs for sensitive endpoint queriesReview API access logs or audit trails for requests to configuration-related API endpoints made by low-privileged users. Look for access to paths that should require elevated privileges.Affected if Low-privileged users have accessed sensitive configuration API endpoints
Environment is affected if running a vulnerable version of EPNM or Prime Infrastructure with API access enabled and low-privileged user accounts present in the system.
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 · scoped8.0.18.1.2
Apply the Cisco security patch for CVE-2025-20270. Until patched, restrict low-privileged user access to sensitive API endpoints and monitor for anomalous API requests.
EPNM: 8.0.1 or 8.1.2; Prime Infrastructure: version > 3.10.6 (contact Cisco for exact patch)
- 1. Identify the currently installed version of Cisco Evolved Programmable Network Manager (EPNM) or Prime Infrastructure
- 2. For EPNM: If running version 7.1.0 or earlier, upgrade to 8.0.1 or later (8.1.2 recommended)
- 3. For EPNM: If running version 8.0.0, upgrade to 8.0.1 or later
- 4. For EPNM: If running version 8.1.0 or 8.1.1, upgrade to 8.1.2
- 5. For Prime Infrastructure: Upgrade to a version higher than 3.10.6 (contact Cisco for specific patch availability)
- 6. After upgrade, verify the fix by confirming the API endpoint now properly validates requests and restricts sensitive configuration information
- 7. Review user permissions to ensure users have only the minimum required privileges
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Evolved Programmable Network Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20270 — 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-2025-20270 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