dbcve.org
Unified CallmanagerApplication · Cisco

CVE-2008-0026

MEDIUM · 6.5 CVSS v2.0 Published 2008-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
SQL injection vulnerability in Cisco Unified CallManager/Communications Manager (CUCM) 5.0/5.1 before 5.1(3a) and 6.0/6.1 before 6.1(1a) allows remote authenticated users to execute arbitrary SQL commands via the key parameter to the (1) admin and (2) user interface pages.

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 confidence

SQL injection vulnerability in Cisco Unified CallManager/Communications Manager allows authenticated remote users to execute arbitrary SQL commands via the 'key' parameter in admin and user interface pages. Affected versions are 5.0/5.1 before 5.1(3a) and 6.0/6.1 before 6.1(1a). An attacker with valid credentials could potentially read, modify, or delete database contents.

MitigationApply Cisco patches 5.1(3a) for version 5.x or 6.1(1a) for version 6.x, or upgrade to a later supported release. If immediate patching is not feasible, restrict network access to admin/user interface pages to trusted IP addresses only and minimize the number of authenticated users with access.

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 CallmanagerApplication
Affected:= 5.0= 5.0\(1\)= 5.0\(2\)= 5.0\(3\)= 5.0\(3a\)= 5.0\(4\)= 5.0_4a= 5.1= 6.0
Unified Communications ManagerApplication
Affected:= 5.0= 5.0_1= 5.0_2= 5.0_3= 5.0_3a= 5.0_4= 5.0_4a= 5.0_4a_su1= 6.0= 6.0_1= 6.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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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 the installed Cisco Unified CallManager/Communications Manager version
    Log into the Cisco server CLI and run the command 'show version' or access the Cisco Unified Reporting tool to generate a system report. The version is also visible in the admin web interface under Help > About.
    Affected if The reported version matches 5.0, 5.0(1), 5.0(2), 5.0(3), 5.0(3a), 5.0(4), 5.0_4a, 5.1, 6.0, 6.0(1), or 6.1, or falls before 5.1(3a) in the 5.x line or before 6.1(1a) in the 6.x line.
  2. Verify the admin and user web interface status
    Attempt to access the admin interface at https://<server>/ccmadmin or the user interface at https://<server>/ccmuser. Check if these endpoints are reachable from the network.
    Affected if The admin or user web interfaces are exposed and accessible over the network.
  3. Confirm valid user accounts exist with access to vulnerable pages
    Review the local user database or Cisco Unified Communications Manager user configuration. Identify accounts with administrator or standard user roles that can access the admin or user interface pages containing the 'key' parameter.
    Affected if There is at least one active user account with credentials that can authenticate to the admin or user interface.
  4. Review access logs for suspicious 'key' parameter usage
    Examine Cisco Unified CallManager web server access logs (located in /var/log/httpd/ or via Cisco Unified Serviceability) for any unusual GET or POST requests containing the 'key' parameter with SQL-like patterns such as quotes, UNION SELECT, or database function calls.
    Affected if Logs show requests to pages containing the 'key' parameter with SQL injection patterns or unexpected syntax.

The environment is affected if the installed version is 5.0 through 5.1 (before 5.1(3a)) or 6.0 through 6.1 (before 6.1(1a)), the admin/user web interface is accessible, and valid credentials exist for those interfaces.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco patches 5.1(3a) for version 5.x or 6.1(1a) for version 6.x, or upgrade to a later supported release. If immediate patching is not feasible, restrict network access to admin/user interface pages to trusted IP addresses only and minimize the number of authenticated users with access.

Fix this in Unified Callmanager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0026 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2008-0026 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