# CVE-2020-36011: Cross-site scripting in n/a

> Remote attackers can inject arbitrary code via multiple fields in the Add Patient Form, potentially compromising user sessions or executing malicious scripts.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jan 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-mxww-cpwx-rp55

## What is CVE-2020-36011?

CVE-2020-36011 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A cross-site scripting (XSS) issue in Add Patient Form in QDOCS Smart Hospital Management System 3.1 allows a remote attacker to inject arbitrary code via the Name, Guardian Name, Email, Address, Remarks, or Any Known Allergies field.

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

## Which versions are affected by CVE-2020-36011?

It affects 1 product.


Products: Qdocs Smart Hospital.

## How do I fix CVE-2020-36011?

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

## Is CVE-2020-36011 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36011 and fix it if it is affected.

What it is: CVE-2020-36011 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-36011 in the wild and no public exploit code.

Affected product: n/a. 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-2020-36011/ (Markdown: https://insights.sbomify.com/CVE-2020-36011/index.md)
```

## Sources

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

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