# CVE-2016-6272: Other in n/a

> Remote attackers can access XML document contents via XPath injection in Epic MyChart, exposing static display strings.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g9q5-3vv9-mx45

## What is CVE-2016-6272?

CVE-2016-6272 is a high-severity vulnerability in n/a, published on 20 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XPath injection vulnerability in Epic MyChart allows remote attackers to access contents of an XML document containing static display strings, such as field labels, via the topic parameter to help.asp. NOTE: this was originally reported as a SQL injection vulnerability, but this may be inaccurate.

Weakness: CWE-91 (XML Injection)

## Which versions are affected by CVE-2016-6272?

It affects 1 product.


Products: Epic Mychart.

## How do I fix CVE-2016-6272?

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

## Is CVE-2016-6272 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-6272 exists.

Public exploit code:

- EPIC MyChart - X-Path Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6272 and fix it if it is affected.

What it is: CVE-2016-6272 is a high-severity vulnerability in n/a, published on 20 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-6272 exists.

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-2016-6272/ (Markdown: https://insights.sbomify.com/CVE-2016-6272/index.md)
```

## Sources

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

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