# CVE-2026-116482: subhajitkhan online-clinic-management-system patientregistration.php cross site scripting


- **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
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-p5px-rmrr-3f5h

## What is CVE-2026-116482?

CVE-2026-116482 is a medium-severity vulnerability in subhajitkhan online-clinic-management-system, published on 26 Oct 2026. 

### Official description

A vulnerability has been found in subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578. Affected is an unknown function of the file patientregistration.php. Such manipulation of the argument pat_name leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.

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-116482?


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

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

## Is CVE-2026-116482 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116482 is a medium-severity vulnerability in subhajitkhan online-clinic-management-system, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116482 in the wild and no public exploit code.

Affected product: subhajitkhan online-clinic-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-116482/ (Markdown: https://insights.sbomify.com/CVE-2026-116482/index.md)
```

## Sources

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

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