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

> Attackers can execute arbitrary JavaScript in users' browsers via crafted URLs in the HAPI FHIR Testpage Overlay module.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 8 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qj2c-3m6w-qr56

## What is CVE-2020-24301?

CVE-2020-24301 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Oct 2020. 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

Users of the HAPI FHIR Testpage Overlay 5.0.0 and below can use a specially crafted URL to exploit an XSS vulnerability in this module, allowing arbitrary JavaScript to be executed in the user's browser. The impact of this vulnerability is believed to be low, as this module is intended for testing and not believed to be widely used for any production purposes.

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

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

It affects 1 product.


Products: Hapifhir Testpage Overlay.

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

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

## Is CVE-2020-24301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24301 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Oct 2020. 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-2020-24301 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-24301/ (Markdown: https://insights.sbomify.com/CVE-2020-24301/index.md)
```

## Sources

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

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