CVE-2026-2177
Analyzed Analyzed - Analysis Complete
Session Fixation Vulnerability in SourceCodester Prison Management Login

Publication date: 2026-02-08

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability has been found in SourceCodester Prison Management System 1.0. The impacted element is an unknown function of the component Login. The manipulation leads to session fixiation. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-08
Last Modified
2026-04-29
Generated
2026-05-06
AI Q&A
2026-02-08
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fast5 prison_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-384 Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-2177 is a critical session fixation vulnerability found in SourceCodester Prison Management System version 1.0, specifically in the Login component.

The vulnerability occurs because the system assigns a session identifier (PHPSESSID) to unauthenticated users accessing the login page but fails to regenerate this session ID after successful administrator login.

This flaw allows an attacker to pre-obtain a valid session ID, trick an administrator into logging in with that session ID, and then hijack the authenticated session by reusing the same session ID.

As a result, the attacker can gain full administrative access without needing to authenticate themselves.


How can this vulnerability impact me? :

This vulnerability allows an attacker to hijack authenticated sessions by fixing a session ID before login and then reusing it after the administrator logs in.

The attacker gains full administrative access to the system, severely compromising its confidentiality, integrity, and availability.

Because the exploit can be performed remotely without authentication and an easy-to-use proof-of-concept is publicly available, the risk of exploitation is high.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring session management behavior during the login process, specifically checking if the PHP session ID (PHPSESSID) is regenerated after successful authentication.'}, {'type': 'paragraph', 'content': 'One way to detect the vulnerability is to capture HTTP requests and responses to the /Admin/login.php page and verify if the session ID remains the same before and after login.'}, {'type': 'list_item', 'content': 'Use tools like curl or wget to perform login requests and observe the Set-Cookie headers for PHPSESSID.'}, {'type': 'list_item', 'content': 'Example command to capture cookies before login: curl -c cookies.txt http://target/Admin/login.php'}, {'type': 'list_item', 'content': 'Example command to perform login using saved cookies and check if session ID changes: curl -b cookies.txt -c cookies.txt -d "username=admin&password=adminpass" http://target/Admin/login.php -v'}, {'type': 'paragraph', 'content': 'If the PHPSESSID remains unchanged after login, it indicates the presence of the session fixation vulnerability.'}] [2, 3]


What immediate steps should I take to mitigate this vulnerability?

[{'type': 'paragraph', 'content': 'The immediate mitigation step is to ensure that the session ID is regenerated upon successful authentication to prevent session fixation.'}, {'type': 'paragraph', 'content': "Specifically, the application should call session_regenerate_id(true) in PHP right after verifying the administrator's credentials and before setting any session variables."}, {'type': 'paragraph', 'content': 'If modifying the application is not possible immediately, consider replacing the affected product with an alternative solution as no known countermeasures or patches are currently available.'}, {'type': 'paragraph', 'content': 'Additionally, monitor and restrict access to the login page and consider implementing multi-factor authentication to reduce the risk of session hijacking.'}] [1, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart