Unity ConnectionApplication · Cisco
CVE-2026-20059
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 Unity Connection could allow an unauthenticated, remote attacker to conduct a reflected 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 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 · moderate confidenceReflected XSS vulnerability in Cisco Unity Connection's web-based management interface due to improper validation of user-supplied input. An attacker can inject malicious scripts via crafted URLs that get reflected back to the user, allowing arbitrary script execution in the context of the interface or access to sensitive browser-based information.
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
Unity ConnectionApplication
<= 12.5= 14.0= 14su1= 14su2= 14su3= 14su3a= 14su4= 14su5= 15.0= 15su1= 15su2= 15su3CVSS 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 Unity Connection is installedCheck for Cisco Unity Connection on the system via installed software packages or by running 'show version' in the admin CLIAffected if The product is not present on the system, this CVE does not apply
-
Identify installed versionRun the appropriate version command in the Cisco Unity Connection CLI (typically 'admin show version' or 'show version') and note the exact version numberAffected if The installed version matches one of the affected versions listed (12.5 and below, or 14.0 through 14su3, or 15.0 through 15su3)
-
Verify web-based management interface is enabledCheck if the web interface is active by attempting to access the management URL or by reviewing interface configuration settings in the CLIAffected if The web management interface is disabled or not accessible, the XSS flaw cannot be exploited through web requests
You are affected if Cisco Unity Connection is installed with an affected version AND the web-based management interface is enabled and 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.
dbcve · scopedApply the vendor patch from Cisco when available. Until then, train users to avoid clicking untrusted links to the management interface and consider restricting access to the management interface to trusted networks only.
Unity Connection 14su3 or later
- Identify the current Unity Connection version via the Administration page or CLI: run show status
- Schedule a maintenance window for the upgrade
- Back up the Unity Connection system and database before upgrading
- Download Unity Connection 14su3 or later from Cisco Software Central
- Follow Cisco upgrade documentation to apply the service update
- Verify the upgrade was successful and the version reflects the patched release
- Test that the web-based management interface functions normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unity Connection
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20059 — 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-2026-20059 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