CVE-2026-2149
Cross-Site Scripting in Patients Waiting Area Queue System
Publication date: 2026-02-08
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pamzey | patients_waiting_area_queue_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-2149 is a cross-site scripting (XSS) vulnerability found in the Patients Waiting Area Queue Management System version 1.0 developed by Patrick Mvuma. It specifically affects the /appointments.php file through the manipulation of the patient_id parameter.'}, {'type': 'paragraph', 'content': 'This vulnerability arises because the application does not properly neutralize user input in the patient_id argument, allowing an attacker to inject malicious scripts.'}, {'type': 'paragraph', 'content': "The attack can be launched remotely without authentication, but it requires some user interaction to execute the malicious script in the context of another user's browser."}] [2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to execute malicious scripts in the browsers of users interacting with the affected system.
Such cross-site scripting attacks can lead to session hijacking, defacement, or redirection to malicious sites, potentially compromising user data or system integrity.
Since the attack can be launched remotely without authentication, it increases the risk of exploitation, especially if users are tricked into interacting with maliciously crafted links or inputs.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying instances of the vulnerable application, specifically the appointments.php file, and testing the patient_id parameter for cross-site scripting (XSS) injection.
One method to find potentially vulnerable targets is using Google dorking with the query: inurl:appointments.php
To test for the vulnerability on your system, you can attempt to inject a simple XSS payload into the patient_id parameter, for example by accessing a URL like: http://[target]/appointments.php?patient_id=<script>alert(1)</script>
If the script executes or the payload is reflected without proper sanitization, the system is vulnerable.
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability.
It is suggested to replace the affected software with an alternative product to avoid the risk.