CVE-2021-1365: Cisco Unified Communications Manager IM & Presence Service SQL Injection Vulnerabilities
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: unified communications manager im and presence service 11.5\(1\)su9; unified communications manager im and presence service 12.5\(1\)su4 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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.
- weakness
- CWE-89
- affected
- Cisco Unified Communications Manager IM and Presence Service
- published ranges
- cisco unified communications manager im and presence service >= 10.5 < 11.5\(1\)su9; cisco unified communications manager im and presence service >= 12.0 < 12.5\(1\)su4
- first unaffected version, by branch
- unified communications manager im and presence service 11.5\(1\)su9; unified communications manager im and presence service 12.5\(1\)su4
- severity
- 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- assigned by
- cisco
- published
- 2021-05-06
check us tools.cisco.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 7 May 2021 | 0.00556 | |
| 6 Jan 2022 | 0.02445 | |
| 4 Feb 2022 | 0.10855 | crossed 0.10 |
| 1 Apr 2022 | 0.01055 | crossed 0.10 |
| 7 Mar 2023 | 0.00084 | scoring model v2023.03.01 |
| 8 Mar 2023 | 0.00084 | |
| 17 Mar 2025 | 0.00142 | scoring model v2025.03.14 |
| 19 Mar 2025 | 0.0016 | |
| 25 Mar 2025 | 0.00155 | |
| 29 Mar 2025 | 0.00339 | |
| 30 Mar 2025 | 0.00155 | |
| 26 Jun 2025 | 0.00169 | |
| 18 Nov 2025 | 0.00191 | |
| 21 Nov 2025 | 0.00169 | |
| 8 May 2026 | 0.00164 | |
| 15 Jun 2026 | 0.01081 | scoring model v2026.06.15 |
16 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: unified communications manager im and presence service 11.5\(1\)su9; unified communications manager im and presence service 12.5\(1\)su4. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-1365', '2026-11-01T23:59:59.999999Z', now());