Evolved Programmable Network ManagerApplication · Cisco
CVE-2025-20269
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, low-privileged, remote attacker to retrieve arbitrary files from the underlying file system on an affected device. This vulnerability is due to insufficient input validation for specific HTTP requests. An attacker could exploit this vulnerability by sending crafted HTTP requests to the web-based management interface on an affected device. A successful exploit could allow the attacker to access sensitive files from 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 · moderate confidenceA path traversal vulnerability in Cisco EPNM and Cisco Prime Infrastructure web-based management interface allows authenticated low-privileged remote attackers to read arbitrary files from the device filesystem by sending crafted HTTP requests with manipulated path traversal sequences (e.g., ../../../etc/passwd). The vulnerability stems from insufficient input validation of URL parameters in specific HTTP endpoints.
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.1.0
Prime InfrastructureApplication
<= 3.9>= 3.10, <= 3.10.6= 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 versionAccess the web-based management interface and check the About or System Information page, or log into the device CLI and run 'show version' or similar version command for Cisco EPNM or Prime InfrastructureAffected if The installed version is Cisco EPNM <= 7.1.0, 8.0.0, or 8.1.0; OR Cisco Prime Infrastructure <= 3.9, 3.10 through 3.10.6, or specifically 3.10.6
-
Confirm the web-based management interface is enabled and accessibleVerify that the HTTP/HTTPS web management interface is active by attempting to reach the login page at the standard web interface URL (typically https://<device-ip>/)Affected if The web-based management interface is exposed and reachable (this is the attack surface for the vulnerability)
-
Review HTTP access logs for path traversal patternsInspect the web server access logs (typically found in /opt/CSCOlumos/mwtts/logs/ or similar product-specific log directories) for entries containing '../' sequences or file paths like /etc/passwd, Windows system files, or other sensitive filesystem locationsAffected if Logs contain requests with path traversal sequences (e.g., ../../../etc/passwd) that indicate exploitation attempts or proof-of-concept testing
You are affected if your Cisco EPNM or Prime Infrastructure version falls within the affected ranges AND the web-based management interface is 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 · scopedApply Cisco security patches when released; until then, restrict access to the web management interface to trusted networks via firewall rules or ACLs, and monitor for suspicious path traversal patterns in HTTP logs.
EPNM: upgrade to 8.2.0 or later; Prime Infrastructure: upgrade to 3.10.7 or later
- 1. Identify the currently installed version of Cisco Evolved Programmable Network Manager (EPNM) or Cisco Prime Infrastructure
- 2. For EPNM: Upgrade to version 8.2.0 or later (the fixed release that addresses CVE-2025-20269)
- 3. For Prime Infrastructure: Upgrade to version 3.10.7 or later (the fixed release that addresses CVE-2025-20269)
- 4. After upgrading, verify the new version is running: Admin > Software Upgrade > Show Version (or equivalent)
- 5. Test that the web-based management interface is accessible and functioning normally after the upgrade
- 6. Confirm the vulnerability is remediated by reviewing the Cisco Security Advisory for this CVE
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Evolved Programmable Network Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20269 — 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-20269 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