# CVE-2023-7173: PHPGurukul Hospital Management System registration.php cross site scripting

> Remote attackers can inject malicious scripts via the First Name field in the registration form of the Hospital Management System.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q58r-g3cw-gj2r

## What is CVE-2023-7173?

CVE-2023-7173 is a medium-severity cross-site scripting vulnerability in Phpgurukul Hospital Management System, published on 30 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in PHPGurukul Hospital Management System 1.0. This affects an unknown part of the file registration.php. The manipulation of the argument First Name leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-249357 was assigned to this vulnerability.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-7173?

It affects 1 product.


Products: Phpgurukul Hospital Management System.

## How do I fix CVE-2023-7173?

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

## Is CVE-2023-7173 being exploited?

There is no known exploitation of CVE-2023-7173 in the wild and no public exploit code.

Public exploit code:

- https://github.com/sharathc213/CVE-2023-7173 (github_poc): https://github.com/sharathc213/CVE-2023-7173

## Other vulnerabilities in Phpgurukul Hospital Management System

- [CVE-2025-56212](https://insights.sbomify.com/CVE-2025-56212/): SQL injection in n/a (critical 9.8)
- [CVE-2025-56214](https://insights.sbomify.com/CVE-2025-56214/): SQL injection in n/a (critical 9.8)
- [CVE-2024-51360](https://insights.sbomify.com/CVE-2024-51360/): Code injection in n/a (critical 9.8)
- [CVE-2020-26629](https://insights.sbomify.com/CVE-2020-26629/): File upload in n/a (critical 9.8)
- [CVE-2023-31498](https://insights.sbomify.com/CVE-2023-31498/): Privilege escalation in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7173 and fix it if it is affected.

What it is: CVE-2023-7173 is a medium-severity cross-site scripting vulnerability in Phpgurukul Hospital Management System, published on 30 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-7173 in the wild and no public exploit code.

Affected product: Phpgurukul Hospital 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-2023-7173/ (Markdown: https://insights.sbomify.com/CVE-2023-7173/index.md)
```

## Sources

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

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