Unified Contact Center ExpressApplication · Cisco
CVE-2025-20375
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 · uneditedA vulnerability in the web UI of Cisco Unified CCX could allow an authenticated, remote attacker to upload and execute arbitrary files. This vulnerability is due to an insufficient input validation associated to specific UI features. An attacker could exploit this vulnerability by uploading a crafted file to the web UI. A successful exploit could allow the attacker to upload arbitrary files to a vulnerable system and execute them, gaining access to the underlying operating system. To exploit this vulnerability, the attacker must have valid administrative credentials.
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 confidenceThis is an arbitrary file upload vulnerability in Cisco Unified CCX's web UI stemming from insufficient input validation on specific UI features. An authenticated attacker with administrative credentials can upload malicious files to the system and execute them, achieving remote code execution on the underlying operating system.
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 Contact Center ExpressApplication
< 12.5\(1\)_su03_es07= 15.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Cisco Unified CCX installed versionAccess the system via CLI or admin web interface and retrieve the current version. On the CLI, use 'show version' or access the Cisco Unified CCX Administration page and navigate to System > Server Properties to view the version information.Affected if The installed version is less than 12.5(1)_su03_es07 OR the installed version is exactly 15.0
-
Verify web UI administrative access is enabledLog into the Cisco Unified CCX Administration interface and check if administrative users can access the file upload features under Application Management or similar upload-enabled sections.Affected if Administrative web UI is accessible and file upload functionality is available to authenticated admins
-
Review web server logs for file upload requestsExamine the Cisco Unified CCX web server logs (typically in /var/log/ or accessible via the admin interface) for POST requests to file upload endpoints, especially those containing suspicious file extensions like .jsp, .php, .exe, or .sh.Affected if Unusual or unauthorized file upload requests are present in the logs, particularly from admin sessions to directories outside expected upload locations
-
Inspect upload directories for unexpected filesCheck common upload directories in the web application root (such as /appmanager/uploads/, /repository/, or custom upload paths configured in the system) for any files with executable extensions or unfamiliar names.Affected if Unexpected files with executable extensions (e.g., .jsp, .asp, .php, .exe, .sh) are found in upload directories
-
Check for signs of code execution on the operating systemReview system processes and cron jobs for unauthorized commands. Use 'ps -ef' via CLI to list running processes and check /var/spool/cron for unexpected cron entries.Affected if Unfamiliar processes are running or unexpected cron jobs exist that were not configured by your administrators
You are affected if your Cisco Unified CCX version is below 12.5(1)_su03_es07 or exactly 15.0 AND the administrative web interface with file upload capability is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.5
Apply Cisco's official patch for CVE-2025-20375 when available. Until then, restrict administrative access to trusted IPs only and monitor for suspicious file uploads.
Upgrade to 12.5(1)_su03_es07 or later for 12.5.x systems; upgrade to the latest 15.0 ES release for 15.x systems
- 1. Identify the current installed version of Cisco Unified CCX by accessing the platform administration interface.
- 2. For systems running a version earlier than 12.5(1)_su03_es07, plan an upgrade to the 12.5(1) ES03 Engineering Special release or later.
- 3. For systems running version 15.0, plan an upgrade to the latest 15.0 Engineering Special release that addresses this vulnerability.
- 4. Download the appropriate upgrade package from the Cisco Software Download Center (https://software.cisco.com/).
- 5. Review the Cisco Unified CCX upgrade guide and release notes for prerequisites and compatibility requirements.
- 6. Ensure you have valid administrative credentials as required for the upgrade process.
- 7. Execute the upgrade during a scheduled maintenance window following Cisco's documented upgrade procedures.
- 8. After upgrade completion, verify the new version is installed and test the system functionality.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unified Contact Center Express
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20375 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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