Evolved Programmable Network ManagerApplication · Cisco
CVE-2025-20287
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) could allow an authenticated, remote attacker to upload arbitrary files to an affected device. This vulnerability is due to improper validation of files that are uploaded to the web-based management interface. An attacker could exploit this vulnerability by sending a crafted file upload request to a specific API endpoint. A successful exploit could allow the attacker to upload arbitrary files to an affected system. To exploit this vulnerability, an attacker must have at least valid Config Managers credentials on 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 confidenceThis is an arbitrary file upload vulnerability in Cisco EPNM's web-based management interface. The lack of proper validation on files being uploaded to a specific API endpoint allows authenticated attackers with Config Manager credentials to upload arbitrary files to the affected system, potentially leading to remote code execution if executable files can be placed and invoked.
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
<= 8.0.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Cisco EPNM is installedIdentify whether Cisco Evolved Programmable Network Manager is deployed in your environment. Look for the EPNM service or web interface accessible on your network.Affected if The product is not installed, you are not affected by this CVE.
-
Check installed EPNM versionAccess the EPNM web-based management interface and navigate to the version information page, or use the command line interface to retrieve the EPNM version. Compare your version to the affected range: any version <= 8.0.0 is vulnerable.Affected if Your EPNM version is 8.0.0 or lower.
-
Verify web management interface is exposedDetermine if the EPNM web-based management interface is accessible from network segments. Check if TCP ports used by EPNM web UI (typically 443 or 8080) are listening on interfaces reachable from untrusted networks.Affected if The web management interface is exposed to untrusted networks, increasing exposure risk.
-
Identify Config Manager user accountsReview user accounts configured in EPNM with Config Manager privileges. Check user management settings within the EPNM administration console.Affected if Active Config Manager user accounts exist, as these credentials are required for exploitation.
-
Audit logs for file upload API activityExamine EPNM server logs for requests to file upload API endpoints, particularly POST requests to upload endpoints. Look for unusual file types or unexpected upload patterns.Affected if Suspicious or unauthorized file upload requests to API endpoints are found in logs.
Your environment is affected if Cisco EPNM version 8.0.0 or lower is installed and the web management interface with Config Manager accounts is accessible, regardless of whether exploitation has occurred.
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's patch when released; until then, restrict access to the EPNM management interface to trusted networks only, enforce strict credential management, and monitor for suspicious file upload activity to the API endpoint.
Cisco EPNM version greater than 8.0.0 (obtain exact fixed release from Cisco security advisory)
- 1. Navigate to the Cisco Evolved Programmable Network Manager (EPNM) admin interface
- 2. Verify current installed version under Administration > System > Software Management
- 3. Access Cisco's official security advisory portal at sec.cloudapps.cisco.com to obtain the specific fixed release version for CVE-2025-20287
- 4. Download the recommended fixed version from Cisco's software download center
- 5. Back up the current EPNM configuration and database
- 6. Follow Cisco's standard upgrade procedure for EPNM, applying the fixed release
- 7. Verify the upgrade was successful and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Evolved Programmable Network Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20287 — 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-20287 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