Evolved Programmable Network ManagerApplication · Cisco
CVE-2024-20514
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 conduct a stored cross-site scripting (XSS) attack against a user of the interface. This vulnerability exists because the web-based management interface does not properly validate user-supplied input. An attacker could exploit this vulnerability by injecting malicious code into a specific page of the interface. 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 this vulnerability, the attacker must have at least a low-privileged account on an 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 XSS vulnerability in Cisco EPNM and Cisco Prime Infrastructure web-based management interface due to improper input validation. An authenticated low-privileged attacker can inject malicious script code into a specific page that executes in the context of other users' browsers when viewed.
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.0
Prime InfrastructureApplication
< 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
- 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 the installed Cisco productAccess the web management interface and check the About or System Information page, or run 'show version' via CLI if availableAffected if The product is Cisco Evolved Programmable Network Manager or Cisco Prime Infrastructure
-
Check the installed versionCompare the running version to the affected ranges: EPNM < 8.0.0 or Prime Infrastructure < 3.10.6. Find this in the web UI footer, About page, or via CLI command 'show version'Affected if The installed version is lower than 8.0.0 for EPNM or lower than 3.10.6 for Prime Infrastructure
-
Verify web-based management interface is enabledConfirm the web-based management interface is accessible and not disabled. Check if HTTPS/HTTP ports (typically 443/80) are listening on the applianceAffected if The web management interface is exposed and accessible to users
-
Confirm low-privileged user access existsCheck if any user accounts with read-only or limited privileges exist in the system. Verify role assignments in the user management section of the web interfaceAffected if Low-privileged (non-admin) user accounts are present and can access the management interface
-
Inspect for injected scripts in affected pagesReview application logs and examine the specific page where XSS could be injected. Check browser console or proxy logs for any stored scripts executing unexpectedlyAffected if Malicious JavaScript code is found stored in the application database or logs
You are affected if Cisco EPNM version is below 8.0.0 or Prime Infrastructure version is below 3.10.6, and the web management interface is accessible to authenticated users.
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.68.0.0
Apply the vendor-provided patch when released. Until then, limit user privileges to the minimum required, monitor administrative interfaces for suspicious activity, and consider network segmentation to reduce attack surface.
Cisco Evolved Programmable Network Manager 8.0.0 or later; Cisco Prime Infrastructure 3.10.6 or later
- 1. Back up the current configuration and data of the affected device before starting the upgrade process
- 2. Obtain the fixed software version: Cisco EPNM 8.0.0 or later, Cisco Prime Infrastructure 3.10.6 or later from Cisco's official download center
- 3. Follow Cisco's standard upgrade procedure for the specific product (refer to Cisco installation and upgrade guides)
- 4. After upgrade, clear browser cache and cookies to remove any potentially cached malicious scripts
- 5. Verify the upgrade was successful by logging into the web-based management interface
- 6. Confirm the XSS vulnerability is remediated by attempting to inject test script in the previously vulnerable input fields
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Evolved Programmable Network Manager
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20514 — 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-2024-20514 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