CVE-2025-20330
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 IM & Presence Service (Unified CM IM&P) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. This vulnerability exists because the web-based management interface does not properly validate user-supplied input. An attacker could exploit this vulnerability by persuading a user to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information.
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 reflected XSS vulnerability in Cisco Unified CM IM&P's web-based management interface. The interface fails to properly validate user-supplied input, allowing an attacker to inject malicious scripts via crafted links. Successful exploitation enables arbitrary script execution in the user's browser context or access to sensitive browser-based information.
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>= 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Unified CM IM&P installationCheck if Cisco Unified Communications Manager IM and Presence Service is installed on the system. This can be done via the Cisco Unified OS Administration interface or by accessing the server directly.Affected if The product is not installed on the system
-
Determine the installed versionAccess the Cisco Unified OS Administration interface and navigate to About > Version, or use the CLI command 'show version' to retrieve the exact version number of the IM&P service.Affected if The installed version is 12.5, 14.0, or any version from 15.0 up to but not including 15su3
-
Verify web management interface is accessibleConfirm the web-based management interface for Cisco Unified CM IM&P is enabled and accessible. Typically this is reachable on port 8443 or 443. Attempt to access the login page.Affected if The web management interface is enabled and reachable over the network
-
Check if the interface accepts user-supplied URL parametersExamine the web interface for parameters that are reflected back in the response without proper sanitization. This is the root cause of the reflected XSS vulnerability.Affected if User-supplied input in URLs is reflected in the interface response without encoding
Your environment is affected if Cisco Unified CM IM&P is installed with a version of 12.5, 14.0, or 15.0 through 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.
dbcve · scoped15su3
Apply the relevant Cisco patch for CVE-2025-20330. Users should be warned not to click untrusted links until the patch is deployed.
Cisco Unified CM IM&P 15su3 (or later); for 14.0 and 12.5 contact Cisco TAC for the specific fixed special update versions
- 1. Identify the current installed version of Cisco Unified Communications Manager IM & Presence Service by accessing the Cisco Unified CM Administration interface and navigating to About > Version
- 2. For version 15.0 and later releases: Upgrade to Cisco Unified CM IM & Presence Service version 15su3 (Software Update 3) or later
- 3. For version 14.0: Upgrade to the equivalent special update that addresses this vulnerability (contact Cisco TAC for the specific 14.0 suX version)
- 4. For version 12.5: Upgrade to the equivalent special update that addresses this vulnerability (contact Cisco TAC for the specific 12.5 suX version)
- 5. After upgrading, clear browser cache and verify the fix by checking the Cisco Unified CM IM & Presence Service version information
- 6. Test that the web-based management interface functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20330 — 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-20330 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