CVE-2026-1146VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1146: 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.1 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 19 Jan 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-26.

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-1146, organizations should implement the following specific measures: 1) Apply strict input validation on the firstName and lastName parameters to allow only expected characters (e.g., alphabetic characters, spaces, hyphens) and reject or sanitize any input containing script or HTML tags. 2) Employ proper output encoding/escaping techniques when rendering user-supplied data in web pages to prevent script execution. 3) Use Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser. 5) Conduct regular security testing, including automated scanning and manual penetration testing, focusing on input handling and XSS vulnerabilities. 6) Educate users and administrators about the risks of XSS and encourage cautious interaction with unexpected or suspicious inputs. 7) Monitor web server and application logs for unusual requests targeting the vulnerable endpoint to detect potential exploitation attempts early. 8) Consider implementing web application firewalls (WAFs) with rules to detect and block XSS attack patterns targeting the affected parameters.

Description

A vulnerability 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 /php/api_register_patient.php. Such manipulation of the argument firstName/lastName leads to cross site scripting. The attack may be performed from remote. The exploit has been disclosed to the public and may be used.

Impact

The impact of this XSS vulnerability can be significant for organizations using the affected queue management system, particularly in healthcare settings where patient data confidentiality and integrity are paramount. Successful exploitation can allow attackers to execute arbitrary scripts in the context of legitimate users, potentially leading to session hijacking, credential theft, or unauthorized actions within the application. This can compromise patient data privacy and trust, disrupt patient management workflows, and potentially lead to regulatory non-compliance with healthcare data protection laws. Additionally, attackers could use the vulnerability to deliver malware or conduct phishing attacks targeting staff or patients. While the vulnerability does not directly affect system availability, the indirect effects of compromised user accounts or data integrity can cause operational disruptions and reputational damage. The medium severity rating reflects these moderate but impactful risks. Organizations worldwide using this system or similar software with comparable vulnerabilities are at risk, especially if they have not implemented adequate input validation or web application security controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:12 UTC

Technical details

References

Community reviews

Related threats