CVE-2026-2150VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2150: SourceCodester Patients Waiting Area Queue Management System · Cross Site Scripting

Affects SourceCodester Patients Waiting Area Queue Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 2026-10-25.

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
SourceCodesterPatients Waiting Area Queue Management System	Affected =1.0	Fixed in–
Patrick MvumaPatients Waiting Area Queue Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-2150, organizations should implement the following specific measures: 1) Apply any available patches or updates from SourceCodester promptly once released. 2) In the absence of official patches, implement strict input validation on the patient_id parameter to allow only expected formats (e.g., numeric IDs) and reject or sanitize any suspicious input. 3) Employ output encoding techniques such as HTML entity encoding to neutralize injected scripts before rendering user-controllable data in the browser. 4) Utilize Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 5) Conduct regular security testing, including automated scanning and manual code reviews, focusing on input handling in web application components. 6) Educate users and staff about the risks of clicking unsolicited links and encourage reporting of suspicious activity. 7) Monitor web server logs for unusual query parameters or repeated attempts to exploit patient_id. 8) Consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block XSS payloads targeting this parameter. These targeted controls go beyond generic advice and address the specific attack vector and environment of this vulnerability.

Description

A flaw has been found in SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System 1.0. Affected by this issue is some unknown functionality of the file /checkin.php. This manipulation of the argument patient_id causes cross site scripting. The attack can be initiated remotely. The exploit has been published and may be used.

Impact

The primary impact of CVE-2026-2150 is the potential compromise of user confidentiality and integrity within the Patients Waiting Area Queue Management System. Attackers exploiting this XSS flaw can execute arbitrary scripts in the context of authenticated users, potentially stealing session tokens, redirecting users to malicious sites, or manipulating displayed information. This can lead to unauthorized access to patient data or manipulation of queue information, undermining trust and privacy. Although availability is not directly affected, successful attacks could disrupt normal operations through phishing or defacement. Healthcare organizations relying on this system may face regulatory compliance issues and reputational damage if patient data is exposed. The medium severity score reflects that while the vulnerability is exploitable remotely without authentication, it requires user interaction, limiting the attack scope. However, given the sensitive nature of healthcare data and the criticality of patient management systems, even moderate vulnerabilities warrant prompt attention to prevent escalation or chaining with other exploits.

Summary

CVE-2026-2150 is a cross-site scripting vulnerability identified in the SourceCodester Patients Waiting Area Queue Management System version 1.0. The vulnerability arises from insufficient input validation or output encoding of the patient_id parameter in the /checkin.php script. An attacker can craft a malicious URL or payload that injects executable JavaScript code into the application’s response, which is then executed in the context of the victim’s browser. This type of reflected XSS attack can be initiated remotely without requiring authentication, relying on social engineering to trick users into clicking malicious links. The CVSS 4.0 base score of 5.3 reflects a medium severity, considering the attack vector is network-based, with low complexity and no privileges required, but requiring user interaction. The impact primarily affects confidentiality and integrity, allowing attackers to steal session cookies, perform actions on behalf of users, or deface web content. The vulnerability does not impact system availability or require special conditions such as sandbox escape. No official patches or updates have been released yet, and no active exploitation has been reported, but the existence of published exploit code increases the risk of future attacks. The vulnerability highlights the importance of proper input sanitization and output encoding in web applications, especially those handling sensitive patient data in healthcare environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats