Cisco Unified Intelligence Center Server-Side Request Forgery Vulnerability

TL;DR 📌

• A vulnerability in the web-based management interface of Cisco Unified Intelligence Center could allow an unauthenticated, remote attacker to conduct a server-side request forgery (SSRF) attack through an affected device. This vulnerability is due to improper input validation for specific HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful…
• No fixed release listed yet; apply mitigations and monitor.
• Workarounds are documented in the advisory.
• CVEs: CVE-2025-20288.

What happened 🕵️‍♂️

A vulnerability in the web-based management interface of Cisco Unified Intelligence Center could allow an unauthenticated, remote attacker to conduct a server-side request forgery (SSRF) attack through an affected device.

This vulnerability is due to improper input validation for specific HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to send arbitrary network requests that are sourced from the affected device.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

Affected products 🖥️

At the time of publication, this vulnerability affected Cisco Unified Intelligence Center, regardless of device configuration, including if it was being used as part of the following Cisco solutions:

Packaged Contact Center Enterprise (Packaged CCE) Unified Contact Center Enterprise (Unified CCE)

This vulnerability also affected Cisco Unified Contact Center Express (Unified CCX) because Cisco Unified CCX includes Cisco Unified Intelligence Center as part of its software bundle.

For information about which Cisco software releases were vulnerable at the time of publication, see the Fixed Software ["#fs"] section of this advisory. See the Details section in the bug ID(s) at the top of this advisory for the most complete and current information.

Fixed software 🔧

Upgrade to the first fixed release in your train (or later):

Workarounds 🧯

There are no workarounds that address this vulnerability.

Risk in context 🎯

Use vendor CVSS for prioritization. Consider exposure and asset criticality.

Fast facts ⚡

• Advisory: cisco-sa-cuis-ssrf-JSuDjeV
• Initial release: 2025-07-16T16:00:00 UTC
• Last updated: 2025-07-16T16:00:00 UTC

For leadership 🧭

Executive summary. Cisco Unified Intelligence Center, and any Packaged CCE, Unified CCE or Unified CCX deployment that bundles it, can be tricked by an unauthenticated attacker into issuing arbitrary outbound network requests from the device itself. There are no workarounds, so remediation depends on scheduling the upgrade to a fixed release rather than applying a temporary mitigation.

Why it matters:

• No authentication is required, so exposure depends purely on whether the CUIC web management interface is reachable, not on stolen credentials or session tokens.
• Because CUIC ships inside Packaged CCE, Unified CCE and Unified CCX, contact centre environments running any of those solutions inherit this flaw even if CUIC itself isn’t the primary interface administrators use.
• A successful SSRF lets the device be used as a proxy to probe or reach internal network resources it can normally access, which is significant for a system that typically sits alongside contact centre and reporting infrastructure.
• Cisco has stated there are no workarounds, meaning the only fix is upgrading, so the vulnerability persists on unpatched systems until that upgrade window is completed.

Now / Next / Later:

• Now: Identify every deployment running Cisco Unified Intelligence Center, including those embedded in Packaged CCE, Unified CCE and Unified CCX, and confirm whether their web management interface is reachable from untrusted networks.
• Next: Schedule the upgrade to the first fixed release for your train — 12.5(1) SU ES05 for the 12.5 line or 12.6(2) ES05 for the 12.6 line — noting that 12.5(1)SU3 and earlier must migrate to a fixed release since no interim patch exists.
• Later: Add CUIC and its embedded presence in CCE/CCX bundles to your asset inventory so future advisories affecting the shared component are tracked and patched across all dependent solutions, not just the standalone product.