Unified Contact Center ExpressApplication · Cisco
CVE-2025-20376
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 file upload mechanisms. An attacker could exploit this vulnerability by uploading a malicious file to the web UI and executing it. A successful exploit could allow the attacker to execute arbitrary commands on the underlying system and elevate privileges to root. 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 · high confidenceA file upload vulnerability in Cisco Unified CCX web UI allows authenticated remote attackers with administrative credentials to upload and execute arbitrary files due to insufficient input validation, enabling command execution on the underlying system with root privileges.
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.
-
Identify if Cisco Unified CCX is installedCheck for the Cisco Unified CCX application by looking for the 'uccx' service or checking common installation directories such as /opt/cisco/uccx or C:\Program Files\Cisco\Unified CCX on Windows. Alternatively, run 'utils system version' from the Cisco CLI if you have OS-level access.Affected if The product Cisco Unified Contact Center Express is not installed on the system.
-
Determine the installed versionFrom the Cisco CCX CLI, run 'show version' or 'utils system version' to retrieve the exact version number. Compare this version against the affected ranges: any version below 12.5(1)_su03_es07 or exactly version 15.0.Affected if The installed version is below 12.5(1)_su03_es07 or is exactly 15.0.
-
Check if the web UI is accessibleVerify if the Cisco Unified CCX web interface is reachable by attempting to access the admin portal URL (typically https://<hostname>/ccxadmin or https://<hostname>/cgi-bin/db2www) from a network-connected host. Confirm the HTTP/HTTPS service is listening on the device.Affected if The web UI is exposed and reachable over the network.
-
Verify administrative accounts existLog into the Cisco CCX CLI or web interface and check for configured administrative users. In the web UI, navigate to User Management > CCX Administrator Accounts. From CLI, use 'show user' or 'show running-config' to list configured admin accounts.Affected if One or more administrative user accounts are configured and enabled for the web interface.
A system is affected if Cisco Unified CCX is installed with a version below 12.5(1)_su03_es07 or exactly version 15.0, the web UI is network-accessible, and administrative credentials can be used to access the upload functionality.
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 the Cisco patch for CVE-2025-20376 when available and enforce least-privilege administrative access controls to reduce the attack surface.
12.5(1)_su03_es07 or later for the 12.5 branch; contact Cisco TAC for 15.0 fix
- 1. Identify the current installed version of Cisco Unified Contact Center Express (UCCX) via the Cisco Unified RTMT or CLI: run 'show version' in the UCCX CLI
- 2. If running a version < 12.5(1)_su03_es07 on the 12.5 branch, plan for upgrade to 12.5(1)_su03_es07 or later
- 3. If running version 15.0, contact Cisco TAC for the specific patch/firmware version addressing this vulnerability, as no fixed version is specified in the advisory
- 4. Ensure you have valid administrative credentials as required for the upgrade process
- 5. Review Cisco upgrade documentation and perform a backup of the UCCX configuration before proceeding
- 6. Apply the upgrade during a scheduled maintenance window following Cisco's recommended upgrade procedures
- 7. After upgrade, verify the version change and confirm the file upload vulnerability is resolved by attempting a benign file upload through the web UI
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-20376 — 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-20376 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