Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2020-37094 is a high-severity Incorrect Implementation of Authentication Algorithm (CWE-303) vulnerability in Espocrm Espocrm. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and IA-5 (Authenticator Management) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2020-37094 is an authentication vulnerability in EspoCRM version 5.8.5 that enables attackers to access other user accounts by manipulating authorization headers. Specifically, attackers can decode and modify Basic Authorization and Espo-Authorization tokens to gain unauthorized access to administrative user information and privileges. The vulnerability is classified under CWE-639 and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity with network accessibility, low attack complexity, and no requirements for privileges or user interaction.
Remote, unauthenticated attackers can exploit this vulnerability over the network by intercepting or crafting modified authorization tokens, allowing them to impersonate other users, including administrators. Successful exploitation grants high-impact access to sensitive data, enables privilege escalation, and potentially disrupts system availability through unauthorized actions.
Advisories and resources for mitigation are available from the vendor at https://www.espocrm.com, an exploit proof-of-concept at https://www.exploit-db.com/exploits/48376, and a detailed privilege escalation advisory at https://www.vulncheck.com/advisories/espocrm-privilege-escalation. The presence of a public exploit on Exploit-DB indicates practical exploitability in unpatched environments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-31008
Vulnerability Data
EspoCRM 5.7.0 prior to 5.9.0 contains an authentication token reuse vulnerability that allows authenticated attackers to bypass two-factor authentication by exploiting token-to-password-hash mapping in application/Espo/Core/Utils/Authentication/Espo.php. Attackers can obtain an authentication token for a controlled account and replay it against any…
more
victim account sharing the same password, since tokens are bound to password hashes rather than unique per-user values, bypassing the victim's 2FA protections.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
CVE enables exploitation of a public-facing web application (EspoCRM) for unauthorized access (T1190) and privilege escalation to admin via auth token manipulation (T1068).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly mitigates CVE-2020-37094 by requiring identification, reporting, and timely remediation of the authentication flaw in EspoCRM through patching or updates.
Requires management of authorization tokens with sufficient strength of mechanism and protection against unauthorized modification, preventing attackers from decoding and forging them.
Enforces approved authorizations based on validated authentication, rejecting access attempts using manipulated Basic Authorization and Espo-Authorization headers.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct implementation of authentication algorithms.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure authentication control directly requires correct implementation of authentication algorithms.
Security testing can detect flawed authentication implementations but does not prevent them by itself.
Cryptography control addresses proper use of authentication algorithms but is broader than authentication alone.
Secure development lifecycle includes verification steps that can catch incorrect authentication implementations.
Application security requirements can specify correct authentication algorithm use but do not guarantee correct implementation.
Secure coding practices reduce the likelihood of incorrect authentication algorithm implementation.