basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2016-3235
CVE-2016-3235 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Office vulnerability

Microsoft Office OLE DLL contains a DLL side-loading vulnerability due to improper input validation, enabling remote code execution when a user opens a crafted document.

Verdict

Today item — known-exploited.

An attacker can achieve remote code execution by exploiting improper library validation in Office OLE functionality. The vulnerability is actively exploited in the wild and requires user interaction to trigger.

CISA KEV Yes · 2021-11-033EPSS 0.43431 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.43431 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Office. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-264 Permissions/Privileges/Access Control — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-264 · Permissions/Privileges/Access ControlAuthorization / access control
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious document containing a reference to a DLL that will be loaded from an attacker-controlled location or a predictable system path.
Business
An employee opens the document, triggering automatic DLL loading that executes attacker code with the user's privileges.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I place a malicious DLL in a location where Office searches during library resolution, exploiting the side-loading flaw.
Business
The organization's systems become compromised, risking data theft, lateral movement, and operational disruption.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.