Unified Intelligence CenterApplication · Cisco
CVE-2021-1395
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 Intelligence Center could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. This vulnerability exists because the web-based management interface 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 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 confidenceA stored cross-site scripting (XSS) vulnerability in Cisco Unified Intelligence Center's web-based management interface allows unauthenticated remote attackers to inject malicious script via improperly validated user input. The attack requires tricking a user into clicking a crafted link, which then executes arbitrary JavaScript in the context of the user's session, potentially exposing sensitive data or performing actions on behalf of the user.
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 Intelligence CenterApplication
<= 12.0\(1\)= 12.5\(1\)
Packaged Contact Center EnterpriseOperating system
all versions
Unified Contact Center EnterpriseOperating system
all versions
Unified Contact Center ExpressOperating system
<= 12.5\(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.
-
Identify the installed Cisco productAccess the system's about page or use CLI commands (show version) to determine if Cisco Unified Intelligence Center, Packaged Contact Center Enterprise, Unified Contact Center Enterprise, or Unified Contact Center Express is installedAffected if Any of these four products is installed
-
Check the installed version against affected rangesUse 'show version' or the web interface about page to determine the exact version number, then compare: CUIC versions <= 12.0(1) or = 12.5(1); PCCE all versions; UCCE all versions; UCCX versions <= 12.5(1)Affected if The installed version falls within any of these affected ranges
-
Determine if web-based management interface is enabledVerify the web management interface is accessible by attempting to reach the application's URL (typically https://<hostname>/cuic) or checking if HTTP/HTTPS services are listening on the management portsAffected if The web management interface is exposed and accessible
-
Review web server access logs for XSS injection attemptsExamine web server logs (typically in /opt/cuic/logs or similar) for suspicious patterns in request parameters such as <script>, javascript:, onerror=, or other HTML/script tags in user input fieldsAffected if Unusual XSS patterns are found in web logs referencing CVE-2021-1395 or similar attack signatures
-
Inspect browser console for stored XSS indicatorsAs an administrator, use a test account to log into the web interface and inspect browser developer console for any script execution errors or injected scripts in the application pagesAffected if Arbitrary JavaScript executes in the browser when viewing application pages
A user is affected if they have any of the four listed Cisco products installed, with a version within the affected ranges, and the web management interface 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.
From vendor dataApply the Cisco security patch for CVE-2021-1395 when available; in the interim, educate users about avoiding clicking untrusted links and consider web application firewall (WAF) deployment to filter XSS attack vectors.
Fix this in Unified Intelligence Center
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1395 — 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-2021-1395 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