Sensitive user data disclosure via expired tokens
Published Mar 13, 2026 · Updated Mar 13, 2026
IBM Sterling Partner Engagement Manager accepts expired access tokens, allowing remote attackers to read sensitive user information. The access-token validation path treats a token as usable after expiration and authorizes requests that expose user data. No current account or user interaction is required, but remote attackers must possess an expired token; IBM has not disclosed the specific endpoints or data fields.
Summary
What happened
IBM Sterling Partner Engagement Manager accepts expired access tokens, allowing remote attackers to read sensitive user information. The access-token validation path treats a token as usable after expiration and authorizes requests that expose user data. No current account or user interaction is required, but remote attackers must possess an expired token; IBM has not disclosed the specific endpoints or data fields.
The record
- CVE
- CVE-2025-13723
- Published
- Mar 13, 2026
- Updated
- Mar 13, 2026
- Vendor
- IBM
- Product
- IBM Sterling Partner Engagement Manager
- Classifications
- CWE-324, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2026CVE publishedPublication date reported by the CVE source.
- Mar 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.2.3.0 <=6.2.3.5
- Affected versionversion=6.2.4.0 <=6.2.4.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo