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

Microsoft Windows vulnerability

Microsoft Windows contains a link following vulnerability (CWE-59) enabling privilege escalation. The flaw is actively exploited in the wild.

Verdict

Today item — known-exploited.

A privilege escalation vulnerability in Windows allows attackers to follow symbolic or hard links to access protected resources or execute code with elevated privileges. Active exploitation indicates immediate risk to unpatched systems.

CISA KEV Yes · 2026-04-133EPSS 0.04601 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
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 2026-04-13).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.04601 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-59 Link Following — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-59 · Link FollowingPath traversal / file
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 symbolic or hard link pointing to a privileged system resource or file.
Business
An attacker gains unauthorized access to sensitive system files or configuration data.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I place the malicious link in a location where a privileged process will follow it during normal operation.
Business
Legitimate system processes inadvertently execute or access attacker-controlled content with elevated rights.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute code or modify system state through the followed link with the privileges of the process that dereferenced it.
Business
The attacker escalates from user-level access to system or administrator privileges on the compromised host.
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)
  • Public PoC available (VulnCheck)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • 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.