CVE-2025-13718
Cleartext Data Exposure in IBM Sterling Partner Engagement Manager
Publication date: 2026-03-13
Last updated on: 2026-03-18
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ibm | sterling_partner_engagement_manager | From 6.2.3 (inc) to 6.2.3.6 (exc) |
| ibm | sterling_partner_engagement_manager | From 6.2.4 (inc) to 6.2.4.3 (exc) |
| ibm | sterling_partner_engagement_manager | From 6.2.3 (inc) to 6.2.3.6 (exc) |
| ibm | sterling_partner_engagement_manager | From 6.2.4 (inc) to 6.2.4.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-319 | The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects IBM Sterling Partner Engagement Manager versions 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2. It allows a remote attacker to obtain sensitive information that is transmitted in cleartext over a communication channel. Because the information is not properly encrypted, unauthorized actors can potentially sniff and capture this data.
How can this vulnerability impact me? :
The impact of this vulnerability is that sensitive information could be exposed to unauthorized parties if they are able to intercept the communication channel. This could lead to information disclosure, potentially compromising confidentiality. However, the vulnerability has a CVSS base score of 3.7, indicating a low severity with limited impact since it requires a remote attacker with high attack complexity and no privileges.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know