# CVE-2026-3171: SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System queue.php cross site scripting

> Remote attackers can inject malicious scripts via the firstname or lastname parameters in queue.php, potentially compromising user sessions or data.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-rjq9-488h-qv7q

## What is CVE-2026-3171?

CVE-2026-3171 is a medium-severity cross-site scripting vulnerability in Patrick Mvuma Patients Waiting Area Queue Management System, published on 25 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A flaw has been found in SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /queue.php. This manipulation of the argument firstname/lastname causes cross site scripting. The attack is possible to be carried out remotely. The exploit has been published and may be used.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-3171?

It affects 1 product.


Products: Pamzey Patients Waiting Area Queue Management System.

## How do I fix CVE-2026-3171?

No fix has been published for CVE-2026-3171 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3171 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3171 exists.

Public exploit code:

- CVE-2026-3171 and CVE-2026-3170 vulnerability disclosure by Archana M (github_poc): https://github.com/archana1122m/CVE-disclosures

## Other vulnerabilities in Patrick Mvuma Patients Waiting Area Queue Management System

- [CVE-2025-64081](https://insights.sbomify.com/CVE-2025-64081/): SQL injection in n/a (critical 9.8)
- [CVE-2026-3817](https://insights.sbomify.com/CVE-2026-3817/): SourceCodester Patients Waiting Area Queue Management System patient-search.php improper authorization (medium 6.9)
- [CVE-2025-13248](https://insights.sbomify.com/CVE-2025-13248/): SourceCodester Patients Waiting Area Queue Management System api_patient_schedule.php sql injection (medium 6.9)
- [CVE-2025-13122](https://insights.sbomify.com/CVE-2025-13122/): SQL injection in Patients Waiting Area Queue Management System (medium 6.9)
- [CVE-2025-63718](https://insights.sbomify.com/CVE-2025-63718/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3171 and fix it if it is affected.

What it is: CVE-2026-3171 is a medium-severity cross-site scripting vulnerability in Patrick Mvuma Patients Waiting Area Queue Management System, published on 25 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3171 exists.

Affected product: Patrick Mvuma Patients Waiting Area Queue Management System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3171/ (Markdown: https://insights.sbomify.com/CVE-2026-3171/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3171
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3171
- OSV: https://osv.dev/vulnerability/CVE-2026-3171

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3171/
Summaries are generated and may contain mistakes; the official description above is the record.