CVE-2025-20156 json
Cisco Meeting Management Client-Server Privilege Escalation Vulnerability
published last yr. modified 4mo ago also EUVD-2025-2156
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
A vulnerability in the REST API of Cisco Meeting Management could allow a remote, authenticated attacker with low privileges to elevate privileges to administrator on an affected device.
This vulnerability exists because proper authorization is not enforced upon REST API users. An attacker could exploit this vulnerability by sending API requests to a specific endpoint. A successful exploit could allow the attacker to gain administrator-level control over edge nodes that are managed by Cisco Meeting Management.
Patch / fix
- cisco meeting_management 3.9.1
Is CVE-2025-20156 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Cisco Cisco Meeting Management
Classification
- Weakness
-
- CWE-274 Improper Handling of Insufficient Privileges
References
-
sec.cloudapps.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-cmm-privesc-uy2Vf8pc
vendor-advisory
-
blog.clamav.net
/2025/01/clamav-142-and-108-security-patch.html
not-applicable
-
sec.cloudapps.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-clamav-ole2-H549rphA
not-applicable
Sources
- CVE List CVE-2025-20156
- NVD CVE-2025-20156
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.