dbcve.org
EdgeWeb browser · Microsoft

CVE-2016-3260

HIGH · 8.8 CVSS v3.0 Published 2016-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
The Microsoft (1) JScript 9, (2) VBScript, and (3) Chakra JavaScript engines, as used in Microsoft Internet Explorer 11, Microsoft Edge, and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability."

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 · high confidence

Memory corruption vulnerability in Microsoft scripting engines (JScript 9, VBScript, Chakra) allows remote attackers to execute arbitrary code via malicious web pages. The vulnerability affects Internet Explorer 11, Microsoft Edge, and related products. Successful exploitation can lead to complete system compromise.

MitigationApply Microsoft security updates KB3175443 (Edge) and KB3175442 (IE). Until patched, restrict JavaScript/VBScript execution or limit browser usage to trusted sites only.

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 data
EdgeWeb browser
Affected:all versions
Internet ExplorerApplication
Affected:= 11

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Internet Explorer 11 installation
    Open a command prompt and run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' to retrieve the installed IE version, or open IE and navigate to 'About Internet Explorer' in the Help menu.
    Affected if The installed version shows Internet Explorer 11 without the KB3175442 update applied.
  2. Identify Microsoft Edge installation
    Open a command prompt and run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' to confirm Windows 10/Windows Server 2016 presence, then check for Edge in 'C:\Windows\SystemApps\Microsoft.Windows.Edge_cw5n1h2txyewy' or via edge://settings/help in the browser.
    Affected if Microsoft Edge is present on the system and the KB3175443 update has not been applied.
  3. Verify security update KB3175442 for Internet Explorer
    Open PowerShell and run 'Get-HotFix -Id KB3175442' or use 'wmic qfe list | findstr KB3175442' to check if the IE security update is installed.
    Affected if The command returns no result, meaning KB3175442 is not installed on a system with IE11.
  4. Verify security update KB3175443 for Microsoft Edge
    Open PowerShell and run 'Get-HotFix -Id KB3175443' or use 'wmic qfe list | findstr KB3175443' to check if the Edge security update is installed.
    Affected if The command returns no result, meaning KB3175443 is not installed on a system with Edge.
  5. Confirm scripting engine exposure
    Check if JScript or VBScript scripting is enabled in the browser by navigating to Internet Options > Security > Custom Level in IE, or check Group Policy settings under 'Computer Configuration > Administrative Templates > Windows Components > Microsoft Edge' for script execution policies.
    Affected if Scripting is allowed (enabled) for the Internet or Intranet zones and the security updates are not present.

A system is affected if it runs Internet Explorer 11 or Microsoft Edge without having the corresponding security updates KB3175442 (IE) or KB3175443 (Edge) installed, allowing remote code execution through malicious web pages using JScript, VBScript, or Chakra scripting engines.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates KB3175443 (Edge) and KB3175442 (IE). Until patched, restrict JavaScript/VBScript execution or limit browser usage to trusted sites only.

Fix this in Edge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-3260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-3260 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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