Unified Intelligent Contact Management EnterpriseApplication · Cisco
CVE-2025-20273
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-based management interface of Cisco Unified Intelligent Contact Management Enterprise could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. This vulnerability is due to insufficient user input validation. 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.
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 confidenceThis is a reflected XSS vulnerability in Cisco Unified Intelligent Contact Management Enterprise's web-based management interface. Due to insufficient user input validation, an attacker can inject malicious script code via crafted URLs. When a legitimate user clicks the malicious link, the script executes in their browser context, enabling session hijacking or information theft.
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 Intelligent Contact Management EnterpriseApplication
<= 15.0\(1\)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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco Unified ICM Enterprise installation and versionLocate the Cisco Unified ICM Enterprise installation and identify the installed version number. Common methods include checking the application's about page, command-line version tools, or installation directories.Affected if The installed version is 15.0(1) or any version lower than 15.0(1).
-
Verify the web-based management interface is enabledCheck if the web management interface service is running and accessible. This may involve checking Windows services, the Cisco ICM service configuration, or attempting to access the web interface URL.Affected if The web-based management interface is enabled and accessible.
-
Determine if the management interface is network-exposedReview network configuration to determine if the web management interface is reachable from network segments outside the trusted internal network.Affected if The management interface is exposed to untrusted network segments or the internet, making it reachable by potential attackers who could deliver malicious links.
-
Inspect URL handling in the management interfaceManually test the web interface by manipulating URL parameters with benign test strings to observe if input is reflected back without proper encoding.Affected if URL parameters are reflected in the response without sanitization or encoding, indicating the XSS vulnerability may be present.
You are affected if Cisco Unified ICM Enterprise version 15.0(1) or lower is installed AND the web-based management interface is enabled and accessible to users who could click malicious links.
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.
From vendor dataApply the vendor-provided security update when available. Until then, educate users not to click untrusted links and consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.
Fix this in Unified Intelligent Contact Management Enterprise
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-20273 — 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-20273 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