CVE-2016-7267
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 · uneditedMicrosoft Excel 2010 SP2, 2013 SP1, 2013 RT SP1, and 2016 misparses file formats, which makes it easier for remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office Security Feature Bypass 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 · moderate confidenceCVE-2016-7267 is a security feature bypass vulnerability in Microsoft Excel 2010 SP2, 2013 SP1, 2013 RT SP1, and 2016 where the application misparses file formats, allowing remote attackers to execute arbitrary code through specially crafted documents.
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= 2010= 2013= 2016CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Identify installed Excel versionOpen Excel, go to File > Account > About Excel, or run 'wmic product where "name like 'Microsoft Excel%'" get version,installdate' in Command PromptAffected if Version is 2010, 2013, or 2016 (including SP2 for 2010, SP1 for 2013, RT SP1 for 2013, and any 2016 release)
-
Confirm Service Pack level for Excel 2010In Excel, go to File > Account > About Excel - the version number will show '14.0.xxxx' where higher numbers indicate service packs appliedAffected if Excel 2010 is present without Service Pack 2 (SP2) applied
-
Confirm Service Pack level for Excel 2013In Excel, go to File > Account > About Excel - the version number will show '15.0.xxxx' where higher numbers indicate service packs appliedAffected if Excel 2013 is present without Service Pack 1 (SP1) applied
-
Check if security update KB3203616 is installedOpen Control Panel > Programs and Features > View installed updates, search for KB3203616; or run 'wmic qfe get HotFixID,InstalledOn | findstr KB3203616'Affected if The security update KB3203616 is NOT installed on the system
Your environment is affected if you have Excel 2010 (any version below SP2), Excel 2013 (any version below SP1), Excel 2013 RT SP1, or Excel 2016 AND the security update KB3203616 has not been installed.
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 Microsoft security updates for the affected Excel versions and advise users to avoid opening documents from untrusted sources.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7267 — 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-7267 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