Menu

Star on GitHub · 3.2k

CVE-2016-6272

7.5 · HIGH

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.…

Published Feb 20, 2018CWE-91EPSS 20.88%

Overview

CVE-2016-6272 is a high-severity vulnerability. It was published on February 20, 2018 and has a CVSS 3.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-6272?

CVE-2016-6272 is a high-severity vulnerability. It was published on February 20, 2018 and has a CVSS 3.0 base score of 7.5 (HIGH).

How severe is CVE-2016-6272?

This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-6272?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-6272?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-6272 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2016

View all