CVE-2016-7206
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site scripting (XSS) vulnerability in Microsoft Edge allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, aka "Microsoft Edge Information Disclosure Vulnerability," a different vulnerability than CVE-2016-7280.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-site scripting (XSS) vulnerability in Microsoft Edge enables remote attackers to inject arbitrary web script or HTML into pages viewed by victims. The vulnerability allows execution of malicious scripts in the context of the vulnerable site, potentially leading to session hijacking, credential theft, or information disclosure. This is a client-side browser vulnerability with medium severity (CVSS 6.1).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Microsoft Edge is installedSearch for edge.exe in typical installation paths: %ProgramFiles(x86)%\Microsoft\Edge\Application\ or %LocalAppData%\Microsoft\Edge\Application\, or check Start Menu for Microsoft EdgeAffected if If edge.exe exists on the system, Microsoft Edge is present and potentially affected by this vulnerability.
-
Determine installed Edge versionRight-click edge.exe, select Properties, then Details tab to view the File Version. Alternatively, open Microsoft Edge, type edge://settings/help in the address bar to see the version number.Affected if Any version of Microsoft Edge is listed as affected in this CVE; compare your version to Microsoft's patched version for CVE-2016-7206.
-
Verify security update KB3202790 is installedOpen Windows Settings > Update & Security > Windows Update > View update history, or run 'wmic qfe list' in Command Prompt to see installed updates. Look for KB3202790 which addresses CVE-2016-7206.Affected if If KB3202790 is NOT listed in installed updates, the Edge security patch for this XSS vulnerability has not been applied.
-
Check browser is in active useReview endpoint configuration or user surveys to determine if Microsoft Edge is configured as a primary or allowed browser in your environment.Affected if If Edge is actively used or permitted, the XSS vulnerability could be exploited against users viewing malicious web content.
A user is affected if Microsoft Edge is installed, the security update KB3202790 is not present, and the browser is in use or permitted in the environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Microsoft security update for CVE-2016-7206 by updating Microsoft Edge to a patched version. Organizations should deploy browser patches through their patch management processes and verify completion across endpoints.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-7206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data