Unified Communications Manager Im And Presence ServiceApplication · Cisco

CVE-2021-1363

HIGH · 8.1 CVSS v3.1 Published 2021-05-06
Fix available
A fix is available. Upgrade to 11.5 / 12.5 or later.
See remediation →
87/100
Remediation priority · High
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
Multiple vulnerabilities in the web-based management interface of Cisco Unified Communications Manager IM & Presence Service could allow an authenticated, remote attacker to conduct SQL injection attacks on an affected system. These vulnerabilities are due to improper validation of user-submitted parameters. An attacker could exploit these vulnerabilities by authenticating to the application and sending malicious requests to an affected system. A successful exploit could allow the attacker to obtain data or modify data that is stored in the underlying database.

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

Multiple SQL injection vulnerabilities exist in the web-based management interface of Cisco Unified Communications Manager IM & Presence Service due to improper validation of user-submitted parameters. An authenticated attacker can send malicious requests containing unsanitized SQL input to obtain or modify data in the underlying database.

MitigationApply the vendor-supplied patches from Cisco for Unified Communications Manager IM & Presence Service and validate that parameterized queries are enforced across all user-input fields in the web management interface.

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 Communications Manager Im And Presence ServiceApplication
Affected:>= 10.5, < 11.5\(1\)su9>= 12.0, < 12.5\(1\)su4

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 CUCM IM&P version
    Log into the Cisco Unified Communications Manager administrative interface and navigate to System > Version, or run the 'show version' command via CLI on the IM&P server
    Affected if The displayed version falls within 10.5 to 11.5(1)su9 (exclusive of 11.5(1)su9) OR 12.0 to 12.5(1)su4 (exclusive of 12.5(1)su4)
  2. Confirm web-based management interface is enabled
    Access the Cisco IM&P Administration portal at the standard HTTPS port (commonly 8443) or check via CLI with 'show network eth0' to identify the management IP and verify the web service is running
    Affected if The web-based management interface is accessible and operational on the target system
  3. Verify authentication method for management portal
    Attempt to access the IM&P web management login page or review the authentication configuration under Cisco Unified Communications Manager > User Management > LDAP
    Affected if The management interface uses local database authentication rather than external LDAP with parameterized query enforcement enabled

The environment is affected if the installed CUCM IM&P version is within the vulnerable ranges (10.5 <= version < 11.5(1)su9 OR 12.0 <= version < 12.5(1)su4) AND the web-based management interface is enabled and uses local database authentication.

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 11.5 / 12.5 or later
Fixed in 11.512.5
Interim mitigation

Apply the vendor-supplied patches from Cisco for Unified Communications Manager IM & Presence Service and validate that parameterized queries are enforced across all user-input fields in the web management interface.

Fix this in Unified Communications Manager Im And Presence Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1363 — 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-2021-1363 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