VulnerabilityPublished 15 Jan 2026

CVE-2026-20075: Cisco Evolved Programmable Network Manager (EPNM) · Cross-site Scripting

Affects Cisco Evolved Programmable Network Manager (EPNM)Source CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CiscoCisco Evolved Programmable Network Manager (EPNM)	Affected =3.0.1 =3.1.2 =1.2 =3.1.1 =3.1.3 =3.1 =3.0.3 =3.0.2 =3.0 =2.2 =1.1 =2.1 =2.0 =4.1 =4.1.1 =4.0.3 =4.0.1 =4.0.2 =4.0 =5.0 =5.0.1 =5.1.1 =5.1 =5.0.2 =5.1.2 =5.1.3 =5.1.4 =6.1.1 =6.1 =6.0.0 =6.0.1 =6.0.2 =7.0.0 =1.2.5 =1.2.6 =2.0.1 =1.2.2 =1.2.3 =1.2.4 =1.2.7 =1.2.1.2 =2.2.1 =2.1.3 =2.0.2 =2.0.3 =2.1.2 =2.0.4 =2.1.1 =5.0.2.5 =5.1.4.3 =6.0.2.1 =6.1.1.1 =5.0.2.1 =5.0.2.2 =5.0.2.3 =5.0.2.4 =5.1.4.1 =5.1.4.2 =2.1.4 =2.2.4 =2.2.3 =2.2.5 =5.1.3.2 =5.1.3.1 =6.0.1.1 =4.1.1.2 =4.1.1.1 =4.0.3.1 =2.0.1.1 =2.1.1.3 =2.1.1.1 =2.1.1.4 =2.0.4.2 =2.0.4.1 =2.1.2.2 =2.1.2.3 =2.0.2.1 =2.1.3.4 =2.1.3.3 =2.1.3.2 =2.1.3.5 =2.2.1.2 =2.2.1.1 =2.2.1.4 =2.2.1.3 =1.2.4.2 =1.2.2.4 =6.0.3 =5.1.4.4 =5.0.2.6 =6.0.3.1 =6.1.2 =6.1.1.2.2 =6.1.2.1 =6.1.2.2 =7.1.1 =7.1.2.1 =7.0.1.3 =7.1.3 =7.1.2 =7.0.1.2 =7.0.1.1 =7.0.1 =7.1.0 =8.0.0 =6.1.2.3 =8.0.0.1 =7.1.3.1 =7.1.4 =8.1.0 =8.1.1 =8.0.1 =8.0.1.1	Fixed in–
CiscoCisco Prime Infrastructure	Affected =3.0.0 =3.1.0 =3.1.5 =2.1 =2.0.0 =3.6.0 =3.7.0 =3.4.0 =3.3.0 =3.2 =3.5.0 =3.2.0-FIPS =2.2 =3.8.0-FED =3.9.0 =3.8.0 =3.10.0 =3.1.1 =2.1.2 =2.2.1 =2.2.0 =3.0.2 =3.0.3 =3.0.1 =2.2.2 =2.2.3 =2.1.0 =2.1.1 =3.9.1 =2.0.10 =3.8.1 =3.7.1 =3.5.1 =3.4.2 =3.3.1 =3.1.7 =3.2.1 =3.2.2 =3.1.6 =3.1.2 =3.4.1 =3.1.3 =3.1.4 =3.0.6 =2.2.10 =3.0.4 =3.0.5 =2.1.56 =2.2.4 =2.2.9 =2.2.8 =2.2.5 =2.2.7 =2.0.39 =3.8_DP1 =3.9_DP1 =3.7_DP2 =3.6_DP1 =3.5_DP4 =3.5_DP2 =3.4_DP10 =3.7_DP1 =3.5_DP3 =3.4_DP11 =3.5_DP1 =3.4_DP8 =3.4_DP1 =3.4_DP3 =3.4_DP5 =3.4_DP2 =3.4_DP7 =3.4_DP6 =3.3_DP4 =3.4_DP4 =3.4_DP9 =3.1_DP16 =3.3_DP2 =3.3_DP3 =3.1_DP15 =3.3_DP1 =3.1_DP13 =3.2_DP2 =3.2_DP1 =3.2_DP3 =3.1_DP14 =3.2_DP4 =3.1_DP7 =3.1_DP10 =3.1_DP11 =3.1_DP4 =3.1_DP6 =3.1_DP12 =3.1_DP5 =3.0.7 =3.1_DP9 =3.1_DP8 =3.10_DP1 =3.10.2 =3.10.3 =3.10 =3.10.1 =3.10.4 =3.10.5 =3.10.6	Fixed in–

AI-suggested

1. Enforce strict administrative access controls: Limit the number of users with administrative privileges and implement multi-factor authentication (MFA) to reduce the risk of credential compromise. 2. Monitor and audit administrative activities within Cisco EPNM and Prime Infrastructure to detect suspicious behavior indicative of exploitation attempts. 3. Apply input validation and output encoding best practices where possible, including reviewing custom scripts or integrations that interact with the management interface. 4. Segregate network management interfaces from general user networks using network segmentation and firewall rules to reduce exposure. 5. Regularly update and patch Cisco EPNM and Prime Infrastructure as soon as official fixes become available from Cisco. 6. Educate administrators about the risks of XSS and the importance of not clicking on suspicious links or executing untrusted scripts within the management interface. 7. Employ web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting the management interface. 8. Conduct periodic security assessments and penetration testing focused on the management interface to identify and remediate any residual input validation issues.

Description

A 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 conduct a stored cross-site scripting (XSS) attack against users of the interface of an affected system. This vulnerability exists because the web-based management interface does not properly validate user-supplied input. An attacker could exploit this vulnerability by inserting malicious code into specific data fields in 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, an attacker must have valid administrative credentials.

Impact

For European organizations, this vulnerability poses a moderate risk primarily due to the requirement for administrative credentials and user interaction. However, given that Cisco EPNM and Prime Infrastructure are widely used for network management and monitoring in large enterprises and service providers, exploitation could lead to unauthorized access to sensitive network management data, session hijacking, or manipulation of network configurations. This could disrupt network operations, compromise confidentiality of network topology and device configurations, and potentially facilitate lateral movement within the network. The impact is particularly significant for critical infrastructure sectors such as telecommunications, finance, and government entities in Europe that rely heavily on Cisco network management solutions. Additionally, the vulnerability could be leveraged in targeted attacks against high-value assets, increasing the risk of espionage or sabotage. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially in environments with weak credential management or insufficient access controls.

References

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-epnm-pi-stored-xss-GEkX8yWK (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jan 2026, 17:08 UTC

Technical details

References

Community reviews

Related threats