Vulnerability5 min readUpdated October 23, 2026

ProxyLogon: the Exchange flaws that opened mail servers

Four flaws in Microsoft Exchange let attackers read mailboxes and take over mail servers without a password. How it worked, who was hit, what to do now.

Illustration: a ring showing the CVSS score 9.8, with the title ProxyLogon

What to do now

  1. Install the current security updates for your Exchange Server; a server without the March 2021 updates is open to these attacks.
  2. Check the server for web shells and other signs of attack, even after updating: the attacks began in January 2021, two months before the fix.
  3. If you cannot keep the server patched within days, consider a hosted mail service; Microsoft’s Exchange Online was not affected.
Year
2021
CVSS 3.1 score
9.8 critical
Exchange servers at risk the day before the fix (nearly that many; not all were hacked)
400,000
days of attacks before a fix existed
58
Why it is on the list
  • Reach met

    Nearly 400,000 Exchange servers were online the day before the fix: systems at risk, not hacked ones (RiskIQ data via Microsoft, March 12, 2021).

  • Mass exploitation met

    Attackers planted web shells on more than 5,000 email servers in over 115 countries, and that is only what one security company saw (ESET, March 10, 2021).

  • Damage not met

    No total of the damage or of the stolen mailboxes is documented.

  • Extraordinary response met

    The US agency CISA issued Emergency Directive 21-02 to federal agencies one day after the fix (CISA, March 3, 2021).

How a vulnerability gets on this list

The record
AffectedMicrosoft Exchange Server 2013, 2016 and 2019, run on an organization's own servers
CVECVE-2021-26855, CVE-2021-26857, CVE-2021-26858, CVE-2021-27065
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)CWE-918, CWE-502, CWE-22
Fixed inSecurity updates of March 2, 2021 for Exchange Server 2013, 2016 and 2019
On CISA's list of exploited vulnerabilities sinceNovember 3, 2021
Found byDEVCORE; Volexity and Dubex reported parts of the attack chain seen in attacks
Timeline
12345
  1. 1Discovered
  2. 2First attacks seen+24 days
  3. 3Reported to the vendor+26 days
  4. 4Fix available+82 days
  5. 5CISA issues Emergency Directive 21-02 to US federal agencies+83 days

On March 2, 2021, Microsoft released emergency updates for Exchange Server, the mail server software that many organizations run on their own machines. The updates closed four flaws that attackers had already been using for two months: without a password, they could read mailboxes and take control of the server. Once the flaws were public, many more groups joined in.

How it worked

Exchange has a front end that receives requests from the internet and passes them on to services behind it. The main flaw, CVE-2021-26855, is a server-side request forgery. An attacker who is not logged in sends a crafted request, and the front end forwards it as if the Exchange server itself had asked. That alone was enough to read mailboxes.

With this access, the attacker used a second flaw, CVE-2021-27065 or CVE-2021-26858, to write a file of their choice to the server. That file was a web shell, a small web page that runs whatever commands the attacker sends to it. A third flaw, CVE-2021-26857, let attackers run code as SYSTEM, the highest rights on Windows.

  1. Attackersends a crafted request, no password needed
  2. Exchange front endforwards it as if the server itself asked
  3. Mailboxescan be read at once
  4. Web shellis written to the server
  5. Serverruns the attacker's commands
The attack chain: the first flaw opens the door, the second plants a web shell that gives the attacker control of the server.

The Taiwanese security company DEVCORE found the first flaw on December 10, 2020. On January 5, 2021, it reported to Microsoft a chain of two flaws that it named ProxyLogon. But the attacks had already started two days earlier, on January 3, the security company Volexity found. Volexity and the company Dubex reported parts of the attack chain they had seen in attacks. Microsoft attributed the first wave to a group it calls HAFNIUM, which it assesses as state-sponsored and operating out of China. These attackers used all four flaws.

Reach and damage

On March 1, 2021, the day before the fix, the security company RiskIQ counted nearly 400,000 Exchange servers reachable from the internet, Microsoft reported. That is the number of servers at risk, not the number of servers that were hacked. By March 9, a bit more than 100,000 were still vulnerable. On March 12, about 82,000 were left to update.

Exchange servers without the fix, March 2021
March 1, the day before the fix400,000
March 9100,000
March 1282,000

RiskIQ counts published by Microsoft, rounded as Microsoft gives them: nearly 400,000, a bit more than 100,000, about 82,000.

No source gives a total of the servers that attackers broke into. The security company ESET found web shells on more than 5,000 email servers in over 115 countries by March 10, 2021. These figures come from ESET’s own products, so they show only part of the picture. ESET counted more than ten different attacker groups, most of them so-called APT groups, teams that spy on targets over long periods.

After the disclosure, criminals moved in as well. By March 25, Microsoft saw web shells from the gang behind the DoejoCrypt ransomware, malware that encrypts files and demands a ransom, on around 1,500 systems. Not all of them reached the stage where files were encrypted. There is no documented total of the damage or of the mailboxes that were stolen.

The fix and the response

Microsoft had planned to ship the fix on its regular monthly patch day, March 9. It released the updates a week early instead, outside its usual schedule. They cover Exchange Server 2013, 2016 and 2019. Exchange Server 2010 received an update as an extra precaution. Microsoft’s cloud service Exchange Online was not affected.

The first three weeks after the fix
12345
  1. 1Microsoft releases the updates, a week earlier than planned
  2. 2The US agency CISA issues Emergency Directive 21-02 to federal agencies+1 day
  3. 3The Dutch volunteer group DIVD has sent more than 42,000 warnings to owners of vulnerable servers+5 days
  4. 4ESET counts more than 5,000 servers with web shells+8 days
  5. 5More than 92 % of the Exchange servers Microsoft knows of are patched or protected+23 days

An emergency directive is an order from CISA that US federal agencies must follow; the first deadline of this one ran out two days after it was issued. In the Netherlands, the volunteers of DIVD scanned the internet for vulnerable servers and warned their owners by email. On November 3, 2021, CISA put all four flaws on the first edition of its list of exploited vulnerabilities.

Two scores for the same flaw

The US National Vulnerability Database rates the main flaw 9.8 of 10. Microsoft rates it 9.1. The difference lies in one detail: Microsoft assumes that this flaw on its own cannot knock the server offline, so it counts no impact on availability.

Severity scores for CVE-2021-26855
Microsoft (CVSS 3.1)9.1
NVD (CVSS 3.1)9.8

Both use version 3.1 of the CVSS scale; they differ only in the impact on availability.

Microsoft counted seven Exchange flaws in its update of March 2, 2021. Four of them were used in the attacks, and these four are what most reports call ProxyLogon today, although DEVCORE’s name strictly covers only its chain of two.

Sources

  1. DEVCORE: ProxyLogon, with the full timeline proxylogon.com
  2. Microsoft: HAFNIUM targeting Exchange servers (March 2, 2021) microsoft.com
  3. Microsoft Security Response Center: security updates for Exchange Server microsoft.com
  4. Microsoft: protecting on-premises Exchange servers (March 12, 2021) microsoft.com
  5. Microsoft: attacks taking advantage of the Exchange flaws (March 25, 2021) microsoft.com
  6. Volexity: active exploitation of the Exchange zero-days volexity.com
  7. ESET: Exchange servers under siege from more than ten attacker groups welivesecurity.com
  8. CISA Emergency Directive 21-02 (closed) cisa.gov
  9. DIVD: scan and warnings to owners of vulnerable Exchange servers csirt.divd.nl
  10. NVD: CVE-2021-26855, with Microsoft's score nvd.nist.gov