Threats / Microsoft / CVE-2018-8581
CVE-2018-8581
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Exchange Server vulnerability
A privilege escalation vulnerability in Microsoft Exchange Server allows attackers to impersonate other users. The flaw has been exploited in the wild and leveraged in ransomware campaigns.
Verdict
Today item, not a backlog item.
This vulnerability presents severe risk due to active exploitation, high EPSS score, and ransomware association. Attackers gain user impersonation capabilities on Exchange infrastructure, enabling lateral movement and data exfiltration at scale.
CISA KEV Yes · 2022-03-034Ransomware use Flagged4EPSS 0.27355 (verify live)5Exploit Weaponized · public PoC6CVSS 7.4 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public 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.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.27355 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) · Affected: Microsoft, Exchange Server. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
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 1205 days after 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.
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 gain initial access to an Exchange Server instance through network exposure or compromised credentials.
Business
Attacker establishes foothold in email infrastructure, a critical business communication channel.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the privilege escalation flaw to impersonate legitimate Exchange users without detection.
Business
Attacker bypasses authentication controls and assumes trusted user identity within the organization.
3
Lateral reach — past segmentation narrative 3
Attacker
I access mailboxes, forwarding rules, and sensitive communications of impersonated users.
Business
Confidential business data, financial records, and strategic communications are exposed to adversaries.
4
Data at risk — exfiltration narrative 4
Attacker
I deploy ransomware payloads or establish persistent backdoors across the Exchange environment.
Business
Organization faces operational shutdown, data encryption, extortion demands, and regulatory compliance violations.
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