Cisco Prime Infrastructure and Evolved Programmable Network Manager Remote Code Execution Vulnerability

published 2019-11-26 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-6855

cvss: 8.1; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 3.3%; EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits: 0; none known

A vulnerability in the REST API of Cisco Prime Infrastructure (PI) and Cisco Evolved Programmable Network Manager (EPNM) could allow an unauthenticated remote attacker to execute arbitrary code with root privileges on the underlying operating system. The vulnerability is due to insufficient input validation during the initial High Availability (HA) configuration and registration process of an affected device. An attacker could exploit this vulnerability by uploading a malicious file during the HA registration period. A successful exploit could allow the attacker to execute arbitrary code with root-level privileges on the underlying operating system. Note: This vulnerability can only be exploited during the HA registration period. See the Details section for more information.

Patch / fix

fixed in 2

cisco prime_infrastructure 3.4.2, 3.5.1
cisco evolved_programmable_network_manager 3.0.2

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 23 mo ago (2024-11-20)

Exploit prediction

3.29% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.1	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	10.0	AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

Cisco Cisco Prime Infrastructure

Classification

Weakness

CWE-20 Improper Input Validation

References

tools.cisco.com /security/center/content/CiscoSecurityAdvisory/cisco-sa-20191106-pi-epn-codex
vendor-advisory

Sources

CVE List CVE-2019-15958
NVD CVE-2019-15958

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary