VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2177: SourceCodester Prison Management System · Session Fixiation

Affects SourceCodester Prison Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SourceCodesterPrison Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate this session fixation vulnerability, organizations should implement the following specific measures: 1) Immediately review and update session management practices to ensure session IDs are regenerated upon successful login, invalidating any pre-existing session identifiers. 2) Enforce secure cookie attributes such as HttpOnly, Secure, and SameSite to reduce session hijacking risks. 3) Restrict access to the prison management system to trusted networks or VPNs to limit exposure to remote attackers. 4) Monitor logs for suspicious session activity or repeated session ID reuse attempts. 5) If possible, apply application-layer firewalls or intrusion detection systems to detect and block session fixation attempts. 6) Engage with the vendor or development team to obtain or develop patches addressing the vulnerability. 7) Conduct security awareness training for administrators to recognize and respond to session-related attacks. 8) Consider implementing multi-factor authentication to reduce the impact of session hijacking. These steps go beyond generic advice by focusing on session regeneration, network segmentation, and proactive monitoring tailored to this vulnerability.

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.

Impact

The primary impact of this vulnerability is unauthorized access through session hijacking, which compromises confidentiality and integrity of the prison management system. Attackers could gain access to sensitive inmate data, manipulate records, or disrupt prison operations. This could lead to privacy violations, legal liabilities, and operational disruptions in correctional facilities. Since the system manages critical security and administrative functions, exploitation could also indirectly affect availability if attackers disrupt sessions or system workflows. The ease of remote exploitation without authentication or user interaction increases the risk of widespread attacks, especially if the system is exposed to the internet or poorly segmented networks. Organizations worldwide using this software face risks of data breaches, operational interference, and reputational damage.

Summary

CVE-2026-2177 identifies a session fixation vulnerability in SourceCodester Prison Management System version 1.0, specifically within an unspecified function of the login component. Session fixation occurs when an attacker sets or forces a known session identifier (session ID) on a victim before authentication, enabling the attacker to hijack the authenticated session once the victim logs in. This vulnerability can be exploited remotely without requiring any authentication or user interaction, making it relatively easy to exploit. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The absence of scope change (SC:N) means the vulnerability affects only the vulnerable component. Although no patches or fixes have been released yet, the public disclosure of the exploit increases the risk of exploitation. The vulnerability could allow attackers to impersonate legitimate users, access sensitive data, or perform unauthorized actions within the prison management system, which typically handles critical information such as inmate records, schedules, and security controls. Given the sensitive nature of the application, exploitation could have serious operational and security consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:42 UTC

Technical details

References

Community reviews

Related threats