Unity ConnectionApplication · Cisco

CVE-2026-20061

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-15
Fix available
A fix is available. Upgrade to after 12.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 web-based management interface of Cisco Unity Connection could allow an authenticated, remote attacker to perform an SQL injection attack against an affected device. To exploit this vulnerability, the attacker must have valid user credentials on the affected device. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP(S) request to the web-based management interface of an affected device. A successful exploit could allow the attacker to view data on the affected device.

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 confidence

SQL injection vulnerability in Cisco Unity Connection's web-based management interface due to insufficient validation of user-supplied input. Authenticated attackers can send crafted HTTP(S) requests to inject malicious SQL queries and view unauthorized data on the affected device.

MitigationApply Cisco's official patch when available; implement proper input validation and parameterized queries in the web management interface code to prevent SQL injection.

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
Affected:<= 12.5= 14.0= 14su1= 14su2= 14su3= 14su3a= 14su4= 14su5= 15.0= 15su1= 15su2= 15su3

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify installed Cisco Unity Connection version
    Use the CLI command 'show version' or access the administration dashboard to determine the exact installed version number
    Affected if Version matches or is within: 12.5 or earlier; 14.0; 14su1; 14su2; 14su3; 14su3a; 14su4; 14su5; 15.0; 15su1; 15su2; or 15su3
  2. Confirm web-based management interface is accessible
    Verify that the Cisco Unity Connection web management interface is reachable via HTTP or HTTPS from network locations where attackers could send requests
    Affected if Web management interface is exposed and accessible to unauthenticated or low-privilege network attackers
  3. Check authentication status for web interface
    Determine whether valid user accounts exist with access to the web management interface, as the attacker requires authentication to exploit this flaw
    Affected if Active user accounts with web interface access are present in the system
  4. Review web server logs for suspicious SQL patterns
    Inspect the web server and application logs for incoming requests containing SQL syntax such as single quotes, UNION statements, or database object names in parameters
    Affected if Logs show requests with SQL injection patterns or unauthorized database query attempts

System is affected if running an affected version with the web management interface enabled and accessible to authenticated attackers

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.

From vendor data
Upgrade available Upgrade to a release after 12.5
Interim mitigation

Apply Cisco's official patch when available; implement proper input validation and parameterized queries in the web management interface code to prevent SQL injection.

Fix this in Unity Connection Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20061 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20061 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