Session hijacking via unrotated login identifier
Published Aug 31, 2023 · Updated Oct 1, 2024
Session fixation in InstantCMS 2 before 2.16.1 allows remote authenticated users to reuse a fixed session identifier after login. The loginComplete and autoLogin paths retain the preauthentication PHP session identifier instead of regenerating it when authentication succeeds. Remote authenticated users must first establish or control that identifier, then can reuse the victim's authenticated session to read session-bound information.
Summary
What happened
Session fixation in InstantCMS 2 before 2.16.1 allows remote authenticated users to reuse a fixed session identifier after login. The loginComplete and autoLogin paths retain the preauthentication PHP session identifier instead of regenerating it when authentication succeeds. Remote authenticated users must first establish or control that identifier, then can reuse the victim's authenticated session to read session-bound information.
The record
- CVE
- CVE-2023-4649
- Published
- Aug 31, 2023
- Updated
- Oct 1, 2024
- Vendor
- InstantCMS Team
- Product
- InstantCMS 2
- Classifications
- CWE-384, T1539
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 31, 2023CVE publishedPublication date reported by the CVE source.
- Oct 1, 2024Record 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=unspecified <2.16.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.
Public exploit references
- Huntr session-fixation bounty reportproof of concept · unverified
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