Security readout for executives and security teams
Plain-English summary
EspoCRM 5.6.4 has a reported weakness that lets a logged-in malicious user infer another user's password hash one character at a time. A password hash is not the password itself, but exposure can support offline cracking and account compromise if hashes are weak or reused.
Executive priority
Treat this as a credential-risk issue for EspoCRM 5.6.4, especially where many users can log in. It is not confirmed as actively exploited in the supplied data, but password hash exposure can create downstream account compromise risk.
Technical view
The CVE describes authenticated password hash enumeration through crafted User API filterList queries against api/v1/User. Public data does not provide CVSS, CWE, affected CPEs, or confirmed fixed versions in the supplied bundle, so validation should focus on EspoCRM 5.6.4 exposure and vendor issue tracking.
Likely exposure
Exposure appears limited to organizations running EspoCRM 5.6.4 where an attacker can authenticate to the application and query the User API. The supplied CVE data does not confirm other affected versions or deployment configurations.
Exploitation context
The source states an authenticated attacker can brute-force a user password hash character by character using crafted filters. CISA KEV status is false in the bundle, and no supplied source confirms active exploitation.
Researcher notes
The public bundle is sparse: no CVSS, CWE, CPE, patch version, or exploitation evidence is included. The key technical claim is authenticated hash enumeration through User API filterList behavior, with GitHub issue 1357 as the primary reference.
Mitigation direction
- Identify any EspoCRM 5.6.4 instances in production or accessible environments.
- Check EspoCRM vendor guidance and issue 1357 for fixed versions or recommended remediation.
- Restrict User API access to necessary trusted roles only.
- Review affected accounts and rotate passwords if hash exposure is suspected.
- Monitor for unusual authenticated api/v1/User filterList query patterns.
Validation and detection
- Confirm the running EspoCRM version for each instance.
- Review application logs for repeated authenticated User API filter queries.
- Check whether non-administrative users can query user records unnecessarily.
- Verify vendor issue guidance before applying updates or configuration changes.
- Document any exposed instances, affected users, and remediation status.
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.
Credential 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-2019-14351 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/espocrm/espocrm/issues/1357CVE reference · x_refsource_MISC
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.