CVE-2025-13718: IBM Sterling Partner Engagement Manager · Cleartext Transmission
Affects IBM Sterling Partner Engagement ManagerSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMSterling Partner Engagement Manager | Affected
| Fixed in– |
Mavencom.ibm/sterling-partner-engagement-managerpkg:maven/com.ibm/sterling-partner-engagement-managerOther threats | Affected
| Fixed in– |
CPE configurations (8)
cpe:2.3:a:ibm:sterling_partner_engagement_manager:6.2.3.0:*:*:*:standard:*:*:*cpe:2.3:a:ibm:sterling_partner_engagement_manager:6.2.3.5:*:*:*:standard:*:*:*cpe:2.3:a:ibm:sterling_partner_engagement_manager:6.2.4.0:*:*:*:standard:*:*:*cpe:2.3:a:ibm:sterling_partner_engagement_manager:6.2.4.2:*:*:*:standard:*:*:*cpe:2.3:a:ibm:sterling_partner_engagement_manager:6.2.3.0:*:*:*:essentials:*:*:*cpe:2.3:a:ibm:sterling_partner_engagement_manager:6.2.3.5:*:*:*:essentials:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-13718, organizations should immediately assess their deployment of IBM Sterling Partner Engagement Manager and identify affected versions. The most effective mitigation is to upgrade to a fixed version once IBM releases patches addressing this vulnerability. In the interim, organizations should enforce the use of strong encryption protocols such as TLS 1.2 or higher for all communication channels involving Sterling Partner Engagement Manager to prevent cleartext transmission. Network segmentation and isolation of systems running the affected software can reduce exposure to unauthorized sniffing. Deploying network-level protections such as encrypted VPN tunnels or IPsec can further secure data in transit. Monitoring network traffic for unusual sniffing or man-in-the-middle activities is advisable. Additionally, reviewing and hardening configuration settings related to communication protocols in Sterling Partner Engagement Manager can help ensure encryption is enabled. Organizations should also educate network administrators and security teams about this vulnerability to maintain vigilance until patches are available.
Description
IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 could allow a remote attacker to obtain sensitive information in cleartext in a communication channel that can be sniffed by unauthorized actors.