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

CVE-2026-1147: 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 25 Oct 2026, 19:02 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 20% 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-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

1. Immediate mitigation should include input validation and output encoding on the 'Reason' parameter in /php/api_patient_schedule.php to neutralize malicious scripts. 2. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3. Employ web application firewalls (WAFs) with rules targeting common XSS attack patterns to block exploit attempts. 4. Restrict access to the queue management system’s web interface to trusted networks or VPNs to reduce exposure. 5. Educate users about the risks of clicking suspicious links or submitting untrusted input. 6. Monitor application logs for unusual input patterns or repeated attempts to exploit the vulnerability. 7. Engage with the vendor or community to obtain or develop official patches or updates addressing this vulnerability. 8. Conduct regular security assessments and penetration tests focusing on input handling and XSS vulnerabilities. 9. Where possible, isolate the queue management system from other critical healthcare infrastructure to limit lateral movement in case of compromise.

Description

A vulnerability was found in SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System 1.0. This affects an unknown part of the file /php/api_patient_schedule.php. Performing a manipulation of the argument Reason results in cross site scripting. It is possible to initiate the attack remotely. The exploit has been made public and could be used.

Impact

The primary impact of this vulnerability is the potential compromise of user confidentiality and integrity through the execution of malicious scripts in users’ browsers. Attackers can hijack user sessions, steal sensitive information such as patient scheduling details, or perform unauthorized actions within the application context. This can lead to privacy violations, reputational damage, and potential regulatory non-compliance for healthcare organizations. Although availability is not directly impacted, successful exploitation could facilitate phishing or social engineering attacks that indirectly disrupt operations. Given the healthcare context, compromised patient data or scheduling information could have downstream effects on patient care coordination. The medium severity rating reflects the moderate risk posed by this vulnerability, balancing ease of exploitation with limited impact scope. Organizations worldwide using this specific queue management system version are at risk, especially those with exposed web interfaces accessible over the internet.

Summary

CVE-2026-1147 identifies a cross-site scripting vulnerability in the SourceCodester Patients Waiting Area Queue Management System version 1.0. The vulnerability is located in the /php/api_patient_schedule.php endpoint, specifically involving the 'Reason' parameter. An attacker can craft malicious input that is not properly sanitized or encoded before being reflected back to users, enabling the injection and execution of arbitrary JavaScript code in the victim’s browser. This type of vulnerability is classified as reflected XSS, which can be triggered remotely without requiring authentication, although it does require some user interaction such as clicking a crafted link or submitting manipulated input. The exploit allows attackers to steal session cookies, perform actions on behalf of the user, or redirect victims to malicious sites, thereby compromising confidentiality and integrity of user data. The vulnerability does not affect availability directly and does not require elevated privileges to exploit. While no active exploitation has been reported, the public availability of exploit code increases the risk of opportunistic attacks. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, partial user interaction, and limited impact on confidentiality and integrity. The affected product is a queue management system used in healthcare or patient service environments, which may contain sensitive patient scheduling information. No official patches or vendor advisories have been linked yet, emphasizing the need for immediate mitigation steps by administrators.

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