CVE-2025-20129
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 chat interface of Cisco Customer Collaboration Platform (CCP), formerly Cisco SocialMiner, could allow an unauthenticated, remote attacker to persuade users to disclose sensitive data. This vulnerability is due to improper sanitization of HTTP requests that are sent to the web-based chat interface. An attacker could exploit this vulnerability by sending crafted HTTP requests to the chat interface of a targeted user on a vulnerable server. A successful exploit could allow the attacker to redirect chat traffic to a server that is under their control, resulting in sensitive information being redirected to the attacker.
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 · moderate confidenceAn open redirect vulnerability in the web-based chat interface of Cisco Customer Collaboration Platform (CCP) allows unauthenticated attackers to craft malicious HTTP requests that redirect chat traffic to attacker-controlled servers. This occurs due to improper sanitization of HTTP requests, enabling sensitive information disclosure through traffic interception.
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= 10.5\(1\)= 10.6\(1\)= 10.6\(2\)= 11.0\(1\)= 11.5\(1\)= 11.5\(1\)su1= 11.6\(1\)= 11.6\(2\)= 12.0\(1\)= 12.0\(1\)es02= 12.0\(1\)es03= 12.0\(1\)es04= 8.5\(1\)= 9.0\(2\)su3es04= 10.0\(1\)su1= 10.0\(1\)su1es04= 10.5\(1\)= 10.5\(1\)su1= 10.5\(1\)su1es10= 10.6\(1\)= 10.6\(1\)su1= 10.6\(1\)su2= 10.6\(1\)su2es04= 10.6\(1\)su3CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 the installed productAccess the system administration interface or use CLI commands to determine if the system is running Cisco Socialminer or Cisco Unified Contact Center Express. Check the product name displayed in the system information or license information page.Affected if The product is Cisco Socialminer or Cisco Unified Contact Center Express and the version matches one of the listed affected versions.
-
Determine the exact software versionLocate the software version through the product's web admin console under Help > About, or via CLI command such as 'show version' or 'utils system version' depending on the platform. Compare the displayed version number against the affected version list.Affected if The installed version exactly matches any of these: Socialminer 10.5(1), 10.6(1), 10.6(2), 11.0(1), 11.5(1), 11.5(1)su1, 11.6(1), 11.6(2), 12.0(1), 12.0(1)es02, 12.0(1)es03, 12.0(1)es04; or Unified Contact Center Express 8.5(1), 9.0(2)su3es04, 10.0(1)su1, 10.0(1)su1es04, 10.5(1), 10.5(1)su1, 10.5(1)
-
Verify the chat interface is enabledAccess the Cisco Socialminer or Unified Contact Center Express administration portal and check the configuration status of the web-based chat interface or Customer Collaboration Platform chat features. Look for chat widget, chat queue, or chat service configuration settings.Affected if The web-based chat interface is active and accessible to end users.
-
Inspect HTTP redirect behavior (if possible)If you have administrative access, review the chat application HTTP response headers or proxy logs when the chat interface processes redirect parameters. Look for the 'Location' header behavior when chat URLs are constructed.Affected if The application allows arbitrary URL values in redirect parameters without validation, permitting redirection to external domains.
You are affected if your system runs a matching affected version of Cisco Socialminer or Unified Contact Center Express and has the web-based chat 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.
From vendor dataApply the Cisco patch when available; until then, consider implementing web application firewall rules to filter suspicious redirect parameters in the chat interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20129 — 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-20129 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