Cisco Enterprise Chat and Email Stored Cross-Site Scripting Vulnerability

TL;DR 📌

• A vulnerability in the web UI of Cisco Enterprise Chat and Email (ECE) could allow an unauthenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface. This vulnerability exists because the web UI does not properly validate user-supplied input. An attacker could exploit this vulnerability by persuading a user of the interface to…
• No fixed release listed yet; apply mitigations and monitor.
• Workarounds are documented in the advisory.
• CVEs: CVE-2025-20310.

What happened 🕵️‍♂️

A vulnerability in the web UI of Cisco Enterprise Chat and Email (ECE) could allow an unauthenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface.

This vulnerability exists because the web UI does not properly validate user-supplied input. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. To successfully exploit this vulnerability, an attacker would need valid agent credentials.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. There is a mitigation that addresses this vulnerability.

Affected products 🖥️

At the time of publication, this vulnerability affected Cisco ECE if it had the inbound email security policy of the rich text content policy disabled.

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.

Determine the Rich Text Content Policy Configuration

To determine the status of the inbound email security policy setting of the Cisco ECE server rich text content policy, connect to the ECE System Console or Cisco Packaged Contact Center Enterprise (PCCE) Single Pane of Glass (SPOG), and choose Digital Channels > Chat and Email > Partition > Security > Rich Text Content Policy.

If the inbound email security policy setting is enabled, the system is not affected by this vulnerability. If the setting is disabled, the system is affected by this vulnerability.

Fixed software 🔧

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

Workarounds 🧯

There are no workarounds that address this vulnerability. However, enabling the inbound email security policy setting of the Cisco ECE server rich text content policy mitigates this vulnerability.

To enable this setting, connect to the UCCE System Console and choose Digital Channels > Chat and Email > Partition > Security > Rich Text Content Policy. Change the inbound email security policy setting to enabled.

While this mitigation has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

Risk in context 🎯

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

Fast facts ⚡

• Advisory: cisco-sa-ece-xss-CbtKtEYc
• Initial release: 2025-07-02T16:00:00 UTC
• Last updated: 2025-07-02T16:00:00 UTC

For leadership 🧭

Executive summary. Risk is Medium (CVSS 6.1) for Cisco, Cisco Enterprise Chat and Email. Vendor fixes are available; prioritize upgrade within 30 days based on environment risk.

Why it matters (exposure drivers):

• Potential service impact and security exposure depend on deployment topology and access paths.
• Treat internet-exposed or multi-tenant management nodes as higher risk.
• Ensure monitoring for abnormal auth/config events until upgrades complete.

Remediation & timing:

• Upgrade to the first fixed release per the table above; schedule an approved change window within 30 days.
• Change risk: low-to-moderate (standard vendor patch). Validate backups and rollback plan.

Now / Next / Later:

• Now: Confirm exposure, identify affected versions, and enable monitoring/alerts.
• Next: Patch according to the fixed software table; verify service health post-change.
• Later: Add control checks to build pipeline/CMDB to block drift to vulnerable trains.