CVE-2025-20272 | Cisco Evolved Programmable Network Manager and Cisco Prime Infrastructure Blind SQL Injection Vulnerability

A vulnerability in a subset of REST APIs of Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager (EPNM) could allow an authenticated, low-privileged, remote attacker to conduct a blind SQL injection attack. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted request to an affected API. A successful exploit could allow the attacker to view data in some database tables on an affected device.

Published: 2025-07-16 Last update: 2025-07-31 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-20272 is rated Low Risk (30.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-20272

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-12 0.06% 0.17% +0.11%
2 2026-04-01 0.04% 0.06% +0.03%
3 2025-12-12 — 0.04% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-20272

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]

Weakness enumeration for CVE-2025-20272

Affected software / configurations for CVE-2025-20272

Vendor Product Version Raw CPE
cisco prime_infrastructure 2.0.0 cpe:2.3:a:cisco:prime_infrastructure:2.0.0:*:*:*:*:*:*:*
cisco prime_infrastructure 2.0.10 cpe:2.3:a:cisco:prime_infrastructure:2.0.10:*:*:*:*:*:*:*
cisco prime_infrastructure 2.0.39 cpe:2.3:a:cisco:prime_infrastructure:2.0.39:*:*:*:*:*:*:*
cisco prime_infrastructure 2.1 cpe:2.3:a:cisco:prime_infrastructure:2.1:*:*:*:*:*:*:*
cisco prime_infrastructure 2.1.0 cpe:2.3:a:cisco:prime_infrastructure:2.1.0:*:*:*:*:*:*:*
cisco prime_infrastructure 2.1.1 cpe:2.3:a:cisco:prime_infrastructure:2.1.1:*:*:*:*:*:*:*
cisco prime_infrastructure 2.1.2 cpe:2.3:a:cisco:prime_infrastructure:2.1.2:*:*:*:*:*:*:*
cisco prime_infrastructure 2.1.56 cpe:2.3:a:cisco:prime_infrastructure:2.1.56:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2 cpe:2.3:a:cisco:prime_infrastructure:2.2:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2.0 cpe:2.3:a:cisco:prime_infrastructure:2.2.0:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2.1 cpe:2.3:a:cisco:prime_infrastructure:2.2.1:-:*:*:*:*:*:*
cisco prime_infrastructure 2.2.1 cpe:2.3:a:cisco:prime_infrastructure:2.2.1:update01:*:*:*:*:*:*
cisco prime_infrastructure 2.2.2 cpe:2.3:a:cisco:prime_infrastructure:2.2.2:-:*:*:*:*:*:*
cisco prime_infrastructure 2.2.2 cpe:2.3:a:cisco:prime_infrastructure:2.2.2:update03:*:*:*:*:*:*
cisco prime_infrastructure 2.2.2 cpe:2.3:a:cisco:prime_infrastructure:2.2.2:update04:*:*:*:*:*:*
cisco prime_infrastructure 2.2.3 cpe:2.3:a:cisco:prime_infrastructure:2.2.3:-:*:*:*:*:*:*
cisco prime_infrastructure 2.2.3 cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update02:*:*:*:*:*:*
cisco prime_infrastructure 2.2.3 cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update03:*:*:*:*:*:*
cisco prime_infrastructure 2.2.3 cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update04:*:*:*:*:*:*
cisco prime_infrastructure 2.2.3 cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update05:*:*:*:*:*:*
cisco prime_infrastructure 2.2.3 cpe:2.3:a:cisco:prime_infrastructure:2.2.3:update06:*:*:*:*:*:*
cisco prime_infrastructure 2.2.4 cpe:2.3:a:cisco:prime_infrastructure:2.2.4:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2.5 cpe:2.3:a:cisco:prime_infrastructure:2.2.5:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2.7 cpe:2.3:a:cisco:prime_infrastructure:2.2.7:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2.8 cpe:2.3:a:cisco:prime_infrastructure:2.2.8:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2.9 cpe:2.3:a:cisco:prime_infrastructure:2.2.9:*:*:*:*:*:*:*
cisco prime_infrastructure 2.2.10 cpe:2.3:a:cisco:prime_infrastructure:2.2.10:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.0 cpe:2.3:a:cisco:prime_infrastructure:3.0.0:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.1 cpe:2.3:a:cisco:prime_infrastructure:3.0.1:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.2 cpe:2.3:a:cisco:prime_infrastructure:3.0.2:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.3 cpe:2.3:a:cisco:prime_infrastructure:3.0.3:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.4 cpe:2.3:a:cisco:prime_infrastructure:3.0.4:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.5 cpe:2.3:a:cisco:prime_infrastructure:3.0.5:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.6 cpe:2.3:a:cisco:prime_infrastructure:3.0.6:*:*:*:*:*:*:*
cisco prime_infrastructure 3.0.7 cpe:2.3:a:cisco:prime_infrastructure:3.0.7:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack10:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack11:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack12:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack13:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack14:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack15:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack16:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack4:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack5:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack6:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack7:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack8:*:*:*:*:*:*
cisco prime_infrastructure 3.1 cpe:2.3:a:cisco:prime_infrastructure:3.1:device_pack9:*:*:*:*:*:*
cisco prime_infrastructure 3.1.0 cpe:2.3:a:cisco:prime_infrastructure:3.1.0:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1.1 cpe:2.3:a:cisco:prime_infrastructure:3.1.1:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1.2 cpe:2.3:a:cisco:prime_infrastructure:3.1.2:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1.3 cpe:2.3:a:cisco:prime_infrastructure:3.1.3:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1.4 cpe:2.3:a:cisco:prime_infrastructure:3.1.4:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1.5 cpe:2.3:a:cisco:prime_infrastructure:3.1.5:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1.6 cpe:2.3:a:cisco:prime_infrastructure:3.1.6:*:*:*:*:*:*:*
cisco prime_infrastructure 3.1.7 cpe:2.3:a:cisco:prime_infrastructure:3.1.7:*:*:*:*:*:*:*
cisco prime_infrastructure 3.2 cpe:2.3:a:cisco:prime_infrastructure:3.2:-:*:*:*:*:*:*
cisco prime_infrastructure 3.2 cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack1:*:*:*:*:*:*
cisco prime_infrastructure 3.2 cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack2:*:*:*:*:*:*
cisco prime_infrastructure 3.2 cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack3:*:*:*:*:*:*
cisco prime_infrastructure 3.2 cpe:2.3:a:cisco:prime_infrastructure:3.2:device_pack4:*:*:*:*:*:*
cisco prime_infrastructure 3.2.0-fips cpe:2.3:a:cisco:prime_infrastructure:3.2.0-fips:*:*:*:*:*:*:*
cisco prime_infrastructure 3.2.1 cpe:2.3:a:cisco:prime_infrastructure:3.2.1:*:*:*:*:*:*:*
cisco prime_infrastructure 3.2.2 cpe:2.3:a:cisco:prime_infrastructure:3.2.2:*:*:*:*:*:*:*
cisco prime_infrastructure 3.3 cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack1:*:*:*:*:*:*
cisco prime_infrastructure 3.3 cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack2:*:*:*:*:*:*
cisco prime_infrastructure 3.3 cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack3:*:*:*:*:*:*
cisco prime_infrastructure 3.3 cpe:2.3:a:cisco:prime_infrastructure:3.3:device_pack4:*:*:*:*:*:*
cisco prime_infrastructure 3.3.0 cpe:2.3:a:cisco:prime_infrastructure:3.3.0:-:*:*:*:*:*:*
cisco prime_infrastructure 3.3.0 cpe:2.3:a:cisco:prime_infrastructure:3.3.0:update01:*:*:*:*:*:*
cisco prime_infrastructure 3.3.1 cpe:2.3:a:cisco:prime_infrastructure:3.3.1:*:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack1:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack10:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack11:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack2:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack3:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack4:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack5:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack6:*:*:*:*:*:*
cisco prime_infrastructure 3.4 cpe:2.3:a:cisco:prime_infrastructure:3.4:device_pack7:*:*:*:*:*:*

References for CVE-2025-20272

cvelogic Threat Intelligence