Unified Communications ManagerApplication · Cisco
CVE-2025-20326
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 unauthenticated, 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 confidenceThis is a CSRF (Cross-Site Request Forgery) vulnerability in the web-based management interface of Cisco Unified Communications Manager and Unified CM Session Management Edition. The lack of proper CSRF protections allows an attacker to trick authenticated users into executing unintended administrative actions via malicious links.
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 ManagerApplication
>= 15.0, < 15su3= 12.5= 14.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Cisco Unified Communications Manager installationIdentify if Cisco Unified Communications Manager or Unified CM Session Management Edition is deployed in your environment. Check for CUCM services, administrative interfaces, or contact your Cisco representative if unsure.Affected if The product is not installed - you are not affected.
-
Determine installed CUCM versionAccess the Cisco Unified Communications Manager Administration interface and navigate to About > Version, or use the CLI command 'show version' via SSH to the CUCM publisher server.Affected if The installed version falls within: 12.5, 14.0, or 15.0 through 15su2 (versions >= 15.0 but < 15su3). Versions outside these ranges or at 15su3 and later are not affected.
-
Verify web management interface is enabledConfirm the Cisco Unified Communications Manager Administration web interface is accessible. This is typically on port 443 or 8443. Check if the service is running via CLI: 'show web-security status' or by attempting to access the admin login page.Affected if The web-based management interface is disabled and inaccessible - the CSRF attack surface does not exist.
-
Assess network exposure of admin interfaceReview firewall rules, ACLs, or load balancer configurations to determine if the CUCM web management interface is accessible from outside trusted network segments. Check for any port 443/8443 rules allowing untrusted network access.Affected if The admin interface is exposed to untrusted/untrusted networks - exploitation is more likely.
You are affected if Cisco Unified Communications Manager or Unified CM Session Management Edition is installed with version 12.5, 14.0, or any 15.x version prior to 15su3, and the web-based management interface is enabled and accessible.
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.
From vendor data15su3
Apply Cisco's patch when available; until then, minimize exposure by restricting web management interface access to trusted networks and educate users about not clicking untrusted links.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20326 — 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-2025-20326 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