Account hijacking via retained pre-authentication session ID
Published Dec 1, 2025 · Updated Dec 1, 2025
Session fixation in Blood Bank Management System 1.0 allows remote attackers to hijack user accounts through a preset PHP session ID. login.php accepts the supplied PHPSESSID, and successful authentication leaves the same identifier active instead of regenerating it. The attack requires a victim to authenticate with the fixed identifier, after which the attacker can reuse it to access the victim's account.
Summary
What happened
Session fixation in Blood Bank Management System 1.0 allows remote attackers to hijack user accounts through a preset PHP session ID. login.php accepts the supplied PHPSESSID, and successful authentication leaves the same identifier active instead of regenerating it. The attack requires a victim to authenticate with the fixed identifier, after which the attacker can reuse it to access the victim's account.
The record
- CVE
- CVE-2025-63529
- Published
- Dec 1, 2025
- Updated
- Dec 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2025CVE publishedPublication date reported by the CVE source.
- Dec 1, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- PHPSESSID retention proof of conceptproof of concept · demonstrated
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