CVE-2025-36115
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 · uneditedIBM Sterling Connect:Express Adapter for Sterling B2B Integrator 5.2.0.00 through 5.2.0.12 does not disallow the session id after use which could allow an authenticated user to impersonate another user on the system.
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 · moderate confidenceIBM Sterling Connect:Express Adapter for Sterling B2B Integrator versions 5.2.0.00-5.2.0.12 fails to invalidate or rotate session IDs after use, allowing an authenticated attacker to reuse a captured or predicted session identifier to impersonate other users on the system. This is a session fixation/impersonation vulnerability stemming from improper session lifecycle management.
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>= 5.2.0.00, < 5.2.0.13CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of IBM Sterling Connect:Express AdapterLocate the product installation directory and check the version file or use the product's built-in version command. Common locations include the bin or version directories within the installation path.Affected if The installed version falls within 5.2.0.00 through 5.2.0.12 inclusive.
-
Locate the session management configuration fileSearch for configuration files related to session handling in the installation directory. Look for files named session, security, or auth configuration in conf or config subdirectories.Affected if A session configuration file exists and does not contain settings for session ID rotation upon login.
-
Examine session cookie or token settingsReview the application's web.xml or equivalent deployment descriptor if accessible. Check for session-config settings and whether session-tracking mode is properly configured.Affected if The session configuration lacks session fixation protection mechanisms such as changing session ID after authentication.
-
Review application logs for session reuse patternsAccess the application logs directory and search for repeated session identifiers or patterns indicating session ID reuse across multiple requests or after logout.Affected if Logs show the same session ID being used after a user logs out and logs back in, indicating no session rotation.
-
Test session behavior during authentication flowIf you have a test environment, perform a login, capture the session identifier, log out, then log in again and verify whether the session identifier changes.Affected if The session identifier remains the same after logout and re-authentication, confirming the vulnerability is present.
A system is affected if it runs IBM Sterling Connect:Express Adapter for Sterling B2B Integrator version 5.2.0.00 through 5.2.0.12 and exhibits unchanged session IDs across authentication cycles.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.2.0.13
Implement proper session invalidation after each use or upon logout, and rotate session IDs upon authentication to prevent session fixation attacks. Upgrade to a version where session IDs are properly disallowed after use.
5.2.0.13
- Back up all current configuration files, custom adapters, and any integration scripts for the IBM Sterling Connect:Express Adapter
- Download IBM Sterling Connect:Express Adapter for Sterling B2B Integrator version 5.2.0.13 or later from IBM Fix Central or your authorized IBM distribution channel
- Stop all running IBM Sterling B2B Integrator services that utilize the Connect:Express Adapter
- Install the upgraded Connect:Express Adapter version 5.2.0.13 using the IBM installation documentation for your platform
- After installation, verify that session IDs are now properly invalidated after use by reviewing the new session management configuration
- Restart the IBM Sterling B2B Integrator services
- Test the fix by verifying that session IDs cannot be reused after logout or session expiration to confirm the session fixation vulnerability is resolved
- Restore any custom configurations from the backup if needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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