# CVE-2018-10571: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in OpenEMR, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 30 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c68g-7h73-cvr5

## What is CVE-2018-10571?

CVE-2018-10571 is a medium-severity cross-site scripting vulnerability in Open-Emr Openemr, published on 30 Apr 2018. 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

Multiple reflected cross-site scripting (XSS) vulnerabilities in OpenEMR before 5.0.1 allow remote attackers to inject arbitrary web script or HTML via the (1) patient parameter to interface/main/finder/finder_navigation.php; (2) key parameter to interface/billing/get_claim_file.php; (3) formid or (4) formseq parameter to interface/orders/types.php; (5) eraname, (6) paydate, (7) post_to_date, (8) deposit_date, (9) debug, or (10) InsId parameter to interface/billing/sl_eob_process.php; (11) form_source, (12) form_paydate, (13) form_deposit_date, (14) form_amount, (15) form_name, (16) form_pid, (17) form_encounter, (18) form_date, or (19) form_to_date parameter to interface/billing/sl_eob_search.php; (20) codetype or (21) search_term parameter to interface/de_identification_forms/find_code_popup.php; (22) search_term parameter to interface/de_identification_forms/find_drug_popup.php; (23) search_term parameter to interface/de_identification_forms/find_immunization_popup.php; (24) id parameter to interface/forms/CAMOS/view.php; (25) id parameter to interface/forms/reviewofs/view.php; or (26) list_id parameter to library/custom_template/personalize.php.

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

## Which versions are affected by CVE-2018-10571?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2018-10571?

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

## Is CVE-2018-10571 being exploited?

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

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10571 and fix it if it is affected.

What it is: CVE-2018-10571 is a medium-severity cross-site scripting vulnerability in Open-Emr Openemr, published on 30 Apr 2018. 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-2018-10571 in the wild and no public exploit code.

Affected product: Open-Emr Openemr. 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-2018-10571/ (Markdown: https://insights.sbomify.com/CVE-2018-10571/index.md)
```

## Sources

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

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