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

Microsoft Windows vulnerability

Microsoft Windows Error Reporting Service vulnerability allows privilege escalation. Actively exploited in the wild.

Verdict

Today item — known-exploited.

A privilege escalation flaw in Windows Error Reporting Service enables attackers to gain elevated system access. The vulnerability is being actively exploited. Patching is critical for systems exposed to untrusted users or network access.

CISA KEV Yes · 2023-07-113EPSS 0.32309 (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
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-07-11).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.32309 — 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 exploit a path traversal or symbolic link weakness in the Error Reporting Service to write or modify files with elevated privileges.
Business
Attackers gain system-level code execution, enabling full system compromise, data theft, and lateral movement within the network.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I escalate from a low-privilege user account to SYSTEM or Administrator level by leveraging the service's improper file handling.
Business
Malicious insiders or compromised user accounts become capable of disabling security controls, installing persistent backdoors, and accessing sensitive data.
3

Lateral reach — past segmentation narrative 3

Attacker
I chain this privilege escalation with other exploits to establish persistent remote access and evade detection mechanisms.
Business
Organizations face prolonged dwell time for attackers, increased risk of data exfiltration, and difficulty in incident response and forensic analysis.
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)
  • 9 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.