dbcve.org
Sterling Partner Engagement ManagerApplication · Ibm

CVE-2025-13718

HIGH · 7.5 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 6.2.3.6 / 6.2.4.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

IBM Sterling Partner Engagement Manager transmits sensitive information in cleartext across communication channels, allowing unauthorized actors on the network to sniff and obtain this data. This is a sensitive data exposure vulnerability likely caused by use of unencrypted HTTP or other non-TLS protocols.

MitigationEnable TLS/HTTPS encryption for all communication channels and ensure proper certificate configuration to prevent network sniffing of sensitive data.

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
Sterling Partner Engagement ManagerApplication
Affected:>= 6.2.3, < 6.2.3.6>= 6.2.4, < 6.2.4.3

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of IBM Sterling Partner Engagement Manager
    Locate the product version through the IBM Sterling system administration console, installation directory files, or version lookup command specific to the IBM Sterling deployment
    Affected if The installed version falls within 6.2.3 through 6.2.3.5 OR 6.2.4 through 6.2.4.2 (these ranges are vulnerable)
  2. Verify communication channel encryption configuration
    Inspect the communication channel configuration settings within the IBM Sterling Partner Engagement Manager admin interface or configuration files to determine if TLS/HTTPS is enforced for all inbound and outbound connections
    Affected if Non-TLS or unencrypted HTTP protocols are enabled or permitted for any sensitive communication channel
  3. Check network listener configurations
    Review the network listener or connector configurations to identify which ports and protocols are in use, looking specifically for cleartext HTTP (port 8080, 80) or other non-encrypted protocols
    Affected if Any sensitive data transmission ports are configured to use unencrypted protocols instead of TLS
  4. Examine certificate configuration status
    Review the SSL/TLS certificate configuration within the product to confirm valid certificates are installed and proper cipher suites are enabled
    Affected if No valid TLS certificates are configured or TLS encryption is explicitly disabled

You are affected if your IBM Sterling Partner Engagement Manager version is 6.2.3.0-6.2.3.5 or 6.2.4.0-6.2.4.2 AND any communication channels transmit data over unencrypted HTTP or non-TLS protocols.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.2.3.6 / 6.2.4.3 or later
Fixed in 6.2.3.66.2.4.3
Interim mitigation

Enable TLS/HTTPS encryption for all communication channels and ensure proper certificate configuration to prevent network sniffing of sensitive data.

Recommended fix High confidence

Upgrade to 6.2.3.6 (if on 6.2.3.x branch) or 6.2.4.3 (if on 6.2.4.x branch)

  1. 1. Identify the currently installed IBM Sterling Partner Engagement Manager version by checking the application version in the admin console or installation directory.
  2. 2. If running version 6.2.3.0 through 6.2.3.5, plan upgrade to version 6.2.3.6.
  3. 3. If running version 6.2.4.0 through 6.2.4.2, plan upgrade to version 6.2.4.3.
  4. 4. Review IBM's upgrade documentation and release notes for the target version before initiating the upgrade.
  5. 5. Perform a full backup of the current system including database and configuration files.
  6. 6. Test the upgrade in a non-production environment first to verify compatibility.
  7. 7. Schedule a maintenance window and apply the upgrade following IBM's standard upgrade procedures.
  8. 8. After upgrade, verify the application starts successfully and all services are running.
Caveat Review release notes for any configuration changes or deprecated features between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sterling Partner Engagement Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13718 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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