User impersonation via session persistence after logout
Published Jun 1, 2025 · Updated Aug 26, 2025
Session expiration failure in IBM Planning Analytics Local 2.0 and 2.1 allows remote authenticated users to impersonate another user. The Planning Analytics Workspace logout flow leaves an existing session valid instead of invalidating it. An authenticated user who obtains another user's still-valid session identifier can reuse it after logout to access that user's data and permitted actions.
Summary
What happened
Session expiration failure in IBM Planning Analytics Local 2.0 and 2.1 allows remote authenticated users to impersonate another user. The Planning Analytics Workspace logout flow leaves an existing session valid instead of invalidating it. An authenticated user who obtains another user's still-valid session identifier can reuse it after logout to access that user's data and permitted actions.
The record
- CVE
- CVE-2025-33005
- Published
- Jun 1, 2025
- Updated
- Aug 26, 2025
- Vendor
- IBM
- Product
- IBM Planning Analytics Local
- Classifications
- CWE-613
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 26, 2025Record 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=2.0
- Affected versionversion=2.1
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