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

CVE-2026-2149: 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-2149, organizations should implement the following specific measures: 1) Apply strict input validation and output encoding on the patient_id parameter in /appointments.php to neutralize malicious scripts. Use established libraries or frameworks that automatically handle XSS prevention. 2) Deploy a Content Security Policy (CSP) to restrict execution of unauthorized scripts in browsers interacting with the system. 3) Conduct a thorough code review of the entire application to identify and remediate other potential XSS vectors. 4) Educate users and administrators about the risks of clicking on suspicious links or inputs that could trigger XSS payloads. 5) Monitor web application logs for unusual input patterns or repeated attempts to exploit the patient_id parameter. 6) If possible, isolate the queue management system behind web application firewalls (WAFs) configured to detect and block XSS attacks. 7) Engage with the vendor or community to obtain patches or updates addressing this vulnerability. 8) Consider implementing multi-factor authentication and session management best practices to reduce the impact of session hijacking if exploitation occurs.

Description

A vulnerability was detected in SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /appointments.php. The manipulation of the argument patient_id results in cross site scripting. It is possible to launch the attack remotely. The exploit is now public and may be used.

Impact

The impact of CVE-2026-2149 on organizations worldwide primarily concerns the confidentiality and integrity of patient data and user sessions within healthcare queue management systems. Successful exploitation can lead to theft of session cookies, enabling attackers to impersonate legitimate users, potentially accessing sensitive patient information or manipulating appointment data. This can result in privacy violations, regulatory non-compliance (e.g., HIPAA in the US, GDPR in Europe), and reputational damage. Additionally, attackers could use the vulnerability to deliver further malware or phishing attacks by redirecting users to malicious sites. Although availability impact is minimal, disruption to patient management workflows could occur if users lose trust or if administrators disable affected functionalities. Healthcare providers and associated third parties relying on this system may face operational challenges and increased risk of data breaches. The public availability of exploit code increases the likelihood of opportunistic attacks, especially in environments lacking robust input validation or security controls.

Summary

CVE-2026-2149 identifies a cross-site scripting (XSS) vulnerability in the Patients Waiting Area Queue Management System version 1.0 developed by SourceCodester. The vulnerability is located in the /appointments.php script, specifically in the handling of the patient_id parameter. Due to insufficient input validation or output encoding, an attacker can inject malicious JavaScript code remotely by manipulating this parameter. The vulnerability does not require authentication or privileges and can be exploited over the network, though it requires user interaction to trigger the malicious script execution in the victim’s browser. The CVSS 4.0 score is 5.3 (medium severity), reflecting the network attack vector, low attack complexity, no privileges required, but requiring user interaction and causing limited integrity impact. The vulnerability can be leveraged to perform session hijacking, steal cookies, redirect users to malicious sites, or perform actions on behalf of the user, compromising confidentiality and integrity of sensitive patient or system data. Although no public patches have been released yet and no known exploits are reported in the wild, the availability of exploit code increases the urgency for mitigation. This vulnerability affects only version 1.0 of the product, which is used in healthcare environments to manage patient queues and appointments, making it a critical component for operational continuity and data privacy in healthcare settings.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats