dbcve.org
Unified Intelligence CenterApplication · Cisco

CVE-2025-20288

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

This is a server-side request forgery (SSRF) vulnerability in Cisco Unified Intelligence Center's web-based management interface. An unauthenticated, remote attacker can send crafted HTTP requests with malicious input to the affected device, causing it to make arbitrary network requests sourced from the compromised device.

MitigationApply the vendor-supplied patch or update to Cisco Unified Intelligence Center. If no patch is immediately available, restrict access to the web-based management interface to trusted networks only.

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
Unified Intelligence CenterApplication
Affected:= 10.5\(1\)= 11.0\(1\)= 11.0\(2\)= 11.0\(3\)= 11.5\(1\)= 11.6\(1\)= 12.0\(1\)= 12.5\(1\)= 12.5\(1\)su= 12.6\(1\)= 12.6\(1\)_es05_et= 12.6\(1\)_et
Unified Contact Center ExpressApplication
Affected:= 10.5\(1\)= 10.5\(1\)su1= 10.5\(1\)su1es10= 10.6\(1\)= 10.6\(1\)su1= 10.6\(1\)su2= 10.6\(1\)su2es04= 10.6\(1\)su3= 10.6\(1\)su3es01= 10.6\(1\)su3es02= 10.6\(1\)su3es03= 11.0\(1\)su1

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco product
    Determine if Cisco Unified Intelligence Center (CUIC) or Cisco Unified Contact Center Express (UCCX) is running on the system. Check system inventory, installed software list, or contact system administrator for product confirmation.
    Affected if The system runs Cisco Unified Intelligence Center or Cisco Unified Contact Center Express
  2. Check installed version against affected ranges
    Retrieve the installed version of the Cisco product. For CUIC, this is typically visible in the About or System Information page of the web management interface, or via CLI commands such as 'show version' at the admin console. Compare the installed version to: CUIC: 10.5(1), 11.0(1), 11.0(2), 11.0(3), 11.5(1), 11.6(1), 12.0(1), 12.5(1), 12.5(1)su, 12.6(1), 12.6(1)_es05_et, 12.6(1)_et. UCCX: 10.5(1), 10.5(1)su1, 10.5(1)su1es10, 10.6(1), 10.6(1)su1, 10.6(1)su2, 10.6(1)su2es04, 10.6(1)su3, 10.6(1)su3es01, 10.6(1)su3es02, 10.6(1)su3es03, 11.0(1)su1.
    Affected if The installed version matches any of the listed affected versions
  3. Confirm web management interface is accessible
    Verify whether the web-based management interface is reachable. This is typically accessed over HTTPS on port 443 or 8443. Check if the interface is exposed to network accessible hosts.
    Affected if The web management interface is accessible from the network (not restricted to localhost or trusted management networks)
  4. Review access logs for suspicious HTTP requests
    Examine web server access logs and proxy logs for unusual inbound requests containing suspicious URL parameters, internal IP addresses (127.0.0.1, 10.x.x.x, 192.168.x.x), or unexpected external hostnames. Look for patterns indicative of SSRF probing.
    Affected if Logs show inbound requests with internal network addresses or unusual URL patterns that could indicate SSRF exploitation attempts

The environment is affected if Cisco Unified Intelligence Center or Cisco Unified Contact Center Express is installed with a version matching any of the affected versions listed and the web management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or update to Cisco Unified Intelligence Center. If no patch is immediately available, restrict access to the web-based management interface to trusted networks only.

Recommended fix Moderate confidence

Fixed release available in Cisco advisory for CVE-2025-20288 (check sec.cloudapps.cisco.com for exact version by product)

  1. 1. Navigate to the Cisco Security Advisories page (sec.cloudapps.cisco.com) and search for CVE-2025-20288
  2. 2. Identify the fixed release version for your specific product (Unified Intelligence Center or Unified Contact Center Express) from the advisory
  3. 3. Back up the current configuration of your affected system
  4. 4. Schedule a maintenance window suitable for production impact
  5. 5. Obtain the fixed software release from Cisco using the Cisco Software Checker or direct download
  6. 6. Follow Cisco's documented upgrade procedure for your specific product version
  7. 7. After upgrade, verify the SSRF vulnerability is resolved by sending a test crafted HTTP request (or confirm via vulnerability scan)
Caveat Refer to Cisco release notes for upgrade path; some version jumps may require intermediate upgrades

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unified Intelligence Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20288 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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