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

Microsoft Exchange Server vulnerability

Microsoft Exchange Server privilege escalation vulnerability enabling unauthorized administrative access. Actively exploited in ransomware campaigns.

Verdict

Today item, not a backlog item.

Critical authentication bypass in Exchange Server allows unauthenticated or low-privileged attackers to escalate to administrative control, facilitating ransomware deployment and data exfiltration at enterprise scale.

CISA KEV Yes · 2021-11-033Ransomware use Flagged3EPSS 0.99987 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
108 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 2021-11-03), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99987 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Exchange Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-287 Improper Authentication — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
APT40 State-sponsored (PRC)

The CISA-led joint advisory AA24-190A names APT40 (tracked in ATT&CK as Leviathan) as a PRC Ministry of State Security group that rapidly weaponizes newly public vulnerabilities, naming the ProxyShell Exchange chain, Log4Shell, and Atlassian Confluence CVEs alongside the group.14

03

Why it matters

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

Front door — unauthenticated access narrative 1

Attacker
Gain initial access to Exchange Server through network exposure or compromised credentials.
Business
Email infrastructure becomes entry point for threat actors targeting organizational data and systems.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Exploit authentication weakness to escalate privileges from limited user to administrator account.
Business
Attacker obtains full control of email system and connected infrastructure without detection.
3

Lateral reach — past segmentation narrative 3

Attacker
Deploy ransomware payload or data exfiltration tools using administrative privileges.
Business
Organization faces operational shutdown, data breach, and extortion demands affecting business continuity.
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)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 108 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.