Threats / Microsoft / CVE-2023-36874
CVE-2023-36874
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
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-115EPSS 0.43409 (verify live)6Exploit Public PoC7CVSS 7.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit 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).
Probability (EPSS)
EPSS 0.43409 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-59 Link Following — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
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