Microsoft Exchange Server 2013 CU23/2016 CU18/2016 CU19/2019 CU7/2019 CU8 unknown vulnerability

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in Microsoft Exchange Server 2013 CU23/2016 CU18/2016 CU19/2019 CU7/2019 CU8 (Groupware Software). It has been classified as very critical. This is going to have an impact on confidentiality, and integrity.

The weakness was disclosed 03/02/2021 as confirmed security guidance (Website). The advisory is shared for download at This vulnerability is traded as CVE-2021-26855 since 02/08/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are unknown but a public exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 03/14/2021).

A public exploit has been developed by Jang (testanull) in Python and been published 2 weeks after the advisory. It is declared as functional. The exploit is shared for download at As 0-day the estimated underground price was around $25k-$100k.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.





CPE 2.3infoedit

CPE 2.2infoedit


Youtube: Not available anymore


VulDB Meta Base Score: 9.3
VulDB Meta Temp Score: 8.6

VulDB Base Score: 9.1
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 9.1
Vendor Vector (Microsoft): 🔒

NVD Base Score: 9.8
NVD Vector: 🔒



VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

NVD Base Score: 🔒


Class: Unknown
CWE: Unknown
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔒
Access: Public
Status: Functional
Author: Jang (testanull)
Programming Language: 🔒
Download: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒


Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍


Recommended: Patch
Status: 🔍

Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Exploit Delay Time: 🔍


02/08/2021 CVE assigned
03/02/2021 +22 days Advisory disclosed
03/02/2021 +0 days Countermeasure disclosed
03/03/2021 +0 days VulDB entry created
03/11/2021 +7 days Exploit disclosed
03/14/2021 +3 days VulDB last update



Status: Confirmed

CVE: CVE-2021-26855 (🔒)
scip Labs:


Created: 03/03/2021 08:22 AM
Updated: 03/14/2021 12:02 PM
Changes: (18) vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai vulnerability_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss2_nvd_basescore vulnerability_cvss3_nvd_basescore
Complete: 🔍
Committer: misc


misc (+1)
1 month ago
Nmap script from Microsoft to detect if an Exchange Server is vulnerable:
misc (+0)
1 month ago
There are 2 different exploits at the moment, one written in python and another in go. The exploit code of Jang was removed by GitHub, and was later made available on Web Archive and GitLab. Here are two links to the exploit code: and

Want to stay up to date on a daily basis?

Enable the mail alert feature now!