VulnerabilityPublished 13 Mar 2026

CVE-2025-13723: IBM Sterling Partner Engagement Manager · Use of a Key Past its Expiration Date

Affects IBM Sterling Partner Engagement ManagerSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMSterling Partner Engagement Manager	Affected >=6.2.3.0 <=6.2.3.5 >=6.2.4.0 <=6.2.4.2	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:*:*:*

AI-suggested

Organizations should monitor IBM's official channels for patches addressing CVE-2025-13723 and apply them promptly once released. In the interim, administrators should audit and tighten token validation mechanisms, ensuring that expired tokens are strictly rejected. Implement additional layers of security such as token revocation lists, shortened token lifetimes, and enhanced logging to detect anomalous token usage. Network-level controls like IP whitelisting and rate limiting can reduce exposure to remote exploitation. Conduct thorough reviews of partner engagement workflows to identify and remediate any reliance on stale tokens. Employ anomaly detection systems to flag unusual access patterns indicative of expired token misuse. Educate staff and partners about the risks associated with token management and enforce strict credential hygiene. Finally, consider deploying web application firewalls (WAFs) with custom rules to block requests containing expired tokens 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 an attacker to obtain sensitive user information using an expired access token

Impact

The primary impact of CVE-2025-13723 is the unauthorized disclosure of sensitive user information due to acceptance of expired access tokens. This compromises confidentiality but does not affect data integrity or system availability. Organizations relying on IBM Sterling Partner Engagement Manager for partner communications and supply chain operations risk exposure of sensitive credentials, business data, or personally identifiable information. Such exposure could facilitate further attacks, including social engineering or targeted intrusions. The ease of exploitation—requiring no authentication or user interaction—raises the risk of automated or opportunistic attacks. While no active exploits are known, the vulnerability could be leveraged by attackers to gain footholds or gather intelligence on business partners. The impact is particularly significant for enterprises with complex partner ecosystems and regulatory requirements for data protection, potentially leading to compliance violations and reputational damage.

CWE-324Use of a Key Past its Expiration Date (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a cryptographic key past its expiration date.
Architecture and Design
Adequate consideration should be put into the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.
Implementation
Replace keys within a period of time proportional to their strength.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7263391 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (8)

Description

AI analysisMachine-generated, updated 13 Mar 2026, 18:48 UTC

WeaknessesCWE-324

Technical details

References

Community reviews

Related threats