# CVE-2016-7239: Cross-site scripting in n/a

> Remote attackers can execute cross-site scripting attacks and obtain sensitive information via the XSS filter in Microsoft Internet Explorer and Edge.

- **Severity:** Low 3.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/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:** 10 Nov 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ggwj-4xw9-ff5x

## What is CVE-2016-7239?

CVE-2016-7239 is a low-severity cross-site scripting vulnerability in Microsoft Edge, published on 10 Nov 2016. 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

The RegEx class in the XSS filter in Microsoft Internet Explorer 9 through 11 and Microsoft Edge allows remote attackers to conduct cross-site scripting (XSS) attacks and obtain sensitive information via unspecified vectors, aka "Microsoft Browser Information Disclosure Vulnerability."

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Microsoft Edge, Microsoft Internet Explorer.

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

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

## Is CVE-2016-7239 being exploited?

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

## Other vulnerabilities in Microsoft Edge

- [CVE-2021-26411](https://insights.sbomify.com/CVE-2021-26411/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7200](https://insights.sbomify.com/CVE-2016-7200/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7201](https://insights.sbomify.com/CVE-2016-7201/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, exploited in the wild)
- [CVE-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7239 is a low-severity cross-site scripting vulnerability in Microsoft Edge, published on 10 Nov 2016. 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-2016-7239 in the wild and no public exploit code.

Affected product: Microsoft Edge. 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-7239/ (Markdown: https://insights.sbomify.com/CVE-2016-7239/index.md)
```

## Sources

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

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