# CVE-2019-8368: OpenEMR v5.0.1-6 allows XSS.


- **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
- **Fix available:** No
- **Published:** 16 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m8w7-p4mm-8fvq

## What is CVE-2019-8368?

CVE-2019-8368 is a medium-severity vulnerability in Open-Emr Openemr, published on 16 Sep 2019. 

### Official description

OpenEMR v5.0.1-6 allows XSS.

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

## Which versions are affected by CVE-2019-8368?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2019-8368?

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

## Is CVE-2019-8368 being exploited?

There is no known exploitation of CVE-2019-8368 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-2019-8368 and fix it if it is affected.

What it is: CVE-2019-8368 is a medium-severity vulnerability in Open-Emr Openemr, published on 16 Sep 2019. 
Exploitation: There is no known exploitation of CVE-2019-8368 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-2019-8368/ (Markdown: https://insights.sbomify.com/CVE-2019-8368/index.md)
```

## Sources

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

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