Security readout for executives and security teams
Plain-English summary
EspoCRM 5.7.0 before 5.9.0 could let a logged-in attacker bypass another user’s two-factor authentication if both accounts use the same password. The issue weakens a key account-protection control and can expose CRM data without requiring user interaction.
Executive priority
Treat as high priority for any vulnerable EspoCRM deployment, especially internet-accessible CRM systems. The business risk is unauthorized access to customer, sales, or operational records despite 2FA being enabled.
Technical view
The vulnerability maps authentication tokens to password hashes rather than unique user values in application/Espo/Core/Utils/Authentication/Espo.php. An authenticated attacker can obtain a token for a controlled account and reuse it against a victim account with the same password hash, bypassing 2FA.
Likely exposure
Exposure is limited to EspoCRM deployments in the vulnerable 5.7.0 to pre-5.9.0 range. The source bundle explicitly identifies EspoCRM 5.7.0 and states versions prior to 5.9.0 are affected.
Exploitation context
The CVE is not listed as KEV, so active exploitation is not established here. However, the source bundle cites an ExploitDB entry, meaning public exploit information exists. Exploitation requires an authenticated attacker and a victim account sharing the same password.
Researcher notes
The key condition is password-hash collision through identical passwords across accounts, not a general unauthenticated bypass. Evidence supports public exploit availability, but not confirmed active exploitation. Validate against the patch commit and advisory before expanding affected-version assumptions.
Mitigation direction
- Upgrade EspoCRM to version 5.9.0 or later, or apply the referenced patch commit.
- Review EspoCRM vendor guidance before relying on temporary workarounds.
- Force password changes where shared or weak passwords may exist.
- Audit 2FA-protected accounts for suspicious sessions and token reuse patterns.
Validation and detection
- Inventory EspoCRM instances and confirm exact running versions.
- Check whether any instance is 5.7.0 or below the 5.9.0 fix boundary.
- Review authentication code or package history for the referenced patch commit.
- Inspect logs for unusual authenticated access across accounts sharing password history.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-303: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-37094 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.6HighVector: 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
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-48376CVE reference, VulnCheck · exploit
- EspoCRM Official Vendor HomepageCVE reference, VulnCheck · product
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck AdvisoryCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Implementation of Authentication Algorithm
Incorrect Implementation of Authentication Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.