CWE
89
Advisory Published
Updated

CVE-2008-0026: SQL Injection

First published: Thu Feb 14 2008(Updated: )

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.

Credit: ykramarz@cisco.com

Affected SoftwareAffected VersionHow to fix
Cisco Unified Communications Manager=5.0_4
Cisco CallManager Express=5.0\(2\)
Cisco Unified Communications Manager=5.0_4a
Cisco Unified Communications Manager=5.0
Cisco CallManager Express=5.0\(3\)
Cisco CallManager Express=5.0\(3a\)
Cisco Unified Communications Manager=5.0_1
Cisco Unified Communications Manager=6.1
Cisco Unified Communications Manager=5.0_4a_su1
Cisco CallManager Express=5.0_4a
Cisco CallManager Express=6.0
Cisco Unified Communications Manager=5.0_3a
Cisco CallManager Express=5.0\(1\)
Cisco CallManager Express=5.0\(4\)
Cisco Unified Communications Manager=5.0_3
Cisco CallManager Express=5.0
Cisco Unified Communications Manager=5.0_2
Cisco Unified Communications Manager=6.0_1
Cisco CallManager Express=5.1
Cisco Unified Communications Manager=6.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2008-0026?

    CVE-2008-0026 has a medium severity rating due to its potential for exploitation via SQL injection.

  • How do I fix CVE-2008-0026?

    To fix CVE-2008-0026, update Cisco Unified CallManager/Communications Manager to version 5.1(3a) or later, and 6.1(1a) or later.

  • Who is affected by CVE-2008-0026?

    CVE-2008-0026 affects remote authenticated users of Cisco Unified CallManager versions 5.0, 5.1, and 6.0 prior to the specified updates.

  • What kind of attack can exploit CVE-2008-0026?

    CVE-2008-0026 can be exploited to execute arbitrary SQL commands, which can lead to unauthorized data access or modification.

  • Is there a workaround for CVE-2008-0026?

    There is no official workaround for CVE-2008-0026; patching the software is the recommended mitigation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203