CVE-2026-1146
Cross-Site Scripting in Patients Queue System API Endpoint
Publication date: 2026-01-19
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 |
|---|---|---|
| sourcecodester | patrick_mvuma_patients_waiting_area_queue_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1146 is a Stored Cross-Site Scripting (XSS) vulnerability in the Patrick Mvuma Patients Waiting Area Queue Management System version 1.0. It occurs in the patient registration functionality, specifically in the /php/api_register_patient.php file, where the firstName and lastName input fields are not properly sanitized or encoded. Malicious input in these fields is stored in the database and later rendered in other parts of the application, such as queue.php and dashboard.php, allowing attackers to execute arbitrary JavaScript code in the context of other users. This can be exploited remotely and requires some user interaction. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts in the browsers of users who view affected pages. This can lead to unauthorized actions performed on behalf of users, theft of session tokens or sensitive information, defacement of web pages, or distribution of malware. Since the vulnerability affects data integrity and user interaction, it can undermine trust in the application and potentially lead to further attacks or data compromise. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable script `/php/api_register_patient.php` on your system or network. You can use Google dorking with the query `inurl:php/api_register_patient.php` to identify potentially vulnerable targets. Additionally, testing the input fields `firstName` and `lastName` with typical XSS payloads such as `"><script>alert('XSS')</script>` and observing if the script executes in the application can confirm the vulnerability. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known countermeasures or patches have been reported. Additionally, avoid using the vulnerable application until a fix is available. Implementing input validation and output encoding on the `firstName` and `lastName` fields can help reduce risk, but the recommended action is to discontinue use of the vulnerable version. [1]