CVE-2022-20787
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 · uneditedA vulnerability in the web-based management interface of Cisco Unified Communications Manager (Unified CM) Software and Cisco Unified CM Session Management Edition (SME) Software could allow an authenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected device. This vulnerability is due to insufficient CSRF protections for the web-based management interface on an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to click a malicious link. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the affected user.
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 confidenceCisco Unified CM and Unified CM SME web-based management interface lacks proper CSRF protection, allowing authenticated attackers to trick users into executing unintended actions via malicious links that exploit the user's session.
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>= 12.5\(1\), < 12.5\(1\)su6>= 14.0, < 14su1CVSS 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
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed productLog into the Cisco Unified CM administration interface and navigate to About > Version, or run 'show version' via CLI to confirm the product name is Cisco Unified Communications Manager or Unified CM SMEAffected if Product is not Cisco Unified Communications Manager or Unified CM SME, then not affected by this CVE
-
Determine the installed versionIn the web interface, go to About > Version to see the exact version number (e.g., 12.5(1), 14.0(1)). Compare this against the affected ranges: 12.5(1) to 12.5(1)su5, or 14.0 to 14.0su1Affected if Version falls within 12.5(1) to 12.5(1)su5 OR 14.0 to 14.0su1 - these versions are vulnerable
-
Confirm web-based management interface is enabledVerify the Cisco Unified CM web interface is accessible by accessing the admin URL (typically https://<server>/ccmadmin). The CSRF vulnerability requires the web management interface to be activeAffected if Web interface is not accessible or disabled - the CSRF attack surface does not exist in this case
-
Check if patches have been appliedIn the web interface under About > Version, look for the SU (Software Update) version number. Vulnerable versions are below 12.5(1)su6 or 14.0su1. The SU number indicates whether the security patch has been installedAffected if SU version is below su6 for 12.5(1) branch or below su1 for 14.0 branch - still vulnerable
User is affected if Cisco Unified Communications Manager or Unified CM SME is running version 12.5(1) through 12.5(1)su5 or 14.0 through 14.0su1, with the web management interface enabled.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped12.514su1
Apply Cisco's security patches when available. As a compensating control, users should avoid clicking untrusted links while authenticated to the management interface.
12.5(1)su6 or later for 12.5.x branch; 14su1 or later for 14.x branch
- 1. Identify the currently installed Cisco Unified Communications Manager version using the CLI command 'show version' or through the web interface.
- 2. For Unified CM 12.5(1) installations: upgrade to version 12.5(1)su6 or later.
- 3. For Unified CM 14.0 installations: upgrade to version 14su1 or later.
- 4. Download the appropriate Cisco Unified CM Service Update from the Cisco Software Download center (requires valid Cisco service contract).
- 5. Before applying to production, test the upgrade in a non-production/staging environment.
- 6. Apply the upgrade during a scheduled maintenance window following Cisco's standard upgrade procedures.
- 7. After upgrade, verify the new version is installed using 'show version' and confirm CSRF protections are in place.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20787 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20787 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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