dbcve.org
Unified Contact Center ExpressApplication · Cisco

CVE-2025-20275

HIGH · 7.8 CVSS v3.1 Published 2025-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 file opening process of Cisco Unified Contact Center Express (Unified CCX) Editor could allow an unauthenticated attacker to execute arbitrary code on an affected device.  This vulnerability is due to insecure deserialization of Java objects by the affected software. An attacker could exploit this vulnerability by persuading an authenticated, local user to open a crafted .aef file. A successful exploit could allow the attacker to execute arbitrary code on the host that is running the editor application with the privileges of the user who launched it.

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 confidence

The vulnerability exists in the file opening process of Cisco Unified CCX Editor, where insecure deserialization of Java objects occurs when parsing .aef files. An attacker crafts a malicious .aef file containing serialized Java objects that, when opened by an authenticated local user in the editor, allows arbitrary code execution with the privileges of the user running the application.

MitigationApply the vendor patch from Cisco for Unified CCX Editor and restrict file handling permissions for local users to prevent opening untrusted .aef files.

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
Affected:= 8.5\(1\)= 9.0\(2\)su3es04= 10.0\(1\)su1= 10.0\(1\)su1es04= 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

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm Cisco Unified CCX Editor is installed
    Locate the Cisco Unified CCX Editor application in the system program files or application directory. Check for the presence of editor executables or related components.
    Affected if The Cisco Unified CCX Editor software is present on the system.
  2. Identify the installed Editor version
    Access the Editor application Help menu, About section, or check the installation directory for version metadata files. Compare the version string against the affected list: 8.5(1), 9.0(2)su3es04, 10.0(1)su1, 10.0(1)su1es04, 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.
    Affected if The installed version matches one of the versions listed in the affected products.
  3. Verify .aef file handling capability exists
    Check if the Editor can open or import .aef files by examining the supported file types in the application or file open dialogs.
    Affected if The .aef file format is supported and processable by the Editor.
  4. Confirm local user authentication context
    Determine whether the system allows local user accounts to log into the workstation where the Editor is installed.
    Affected if Local authenticated users have access to log in and run the Editor application.

A user is affected if Cisco Unified CCX Editor is installed, runs one of the listed vulnerable versions, supports .aef file parsing, and local users can authenticate to open such files.

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 patch from Cisco for Unified CCX Editor and restrict file handling permissions for local users to prevent opening untrusted .aef files.

Recommended fix Moderate confidence

Unified CCX 10.0(2) or later fixed release (consult Cisco advisory for exact version)

  1. 1. Identify the current Unified CCX Editor version installed by checking the application or using 'show version' in the Unified CCX CLI
  2. 2. Access Cisco Software Download portal at https://software.cisco.com/ and navigate to Unified Contact Center Express (Unified CCX)
  3. 3. Download the fixed release version for your major release line (10.0(2) or later recommended)
  4. 4. Apply the update following the Unified CCX upgrade guide: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/ccx/upgrading/b_upgrading_ccx.html
  5. 5. Verify the upgrade was successful by checking the version in Unified CCX Administration > System > Configuration > Version Info
  6. 6. Ensure all local users are informed not to open .aef files from untrusted sources
Caveat Review Cisco Unified CCX release notes for any compatibility changes or feature modifications between your current and target version before upgrading

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

Fix this in Unified Contact Center Express Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20275 — 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-20275 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