EUVD-2026-95020
GHSA-8wxm-j7r5-j4mp
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with Email Account scope
-
DeliveryObtain victim's Email Account record ID
-
ExploitRequest record via PersonalAccount\Service IDOR
-
ExecutionExtract disclosed IMAP password
-
ImpactLog into victim mailbox and exfiltrate email
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V6 - Authentication Credential protection in transit/storage
|
| Exploitation Conditions | Exploitation requires an authenticated EspoCRM account that has been granted 'Email Account scope' access (PR:L), and the attacker must know or enumerate the target's Email Account record ID. The vulnerable code path is PersonalAccount\Service, and the affected deployment is any EspoCRM instance before version 10.0.5. Limiting factors: this is not remotely exploitable by anonymous users - a valid authenticated session with the relevant scope is mandatory, which scopes realistic risk to malicious insiders or attackers who have already compromised a low-privilege account; no special non-default configuration is otherwise needed. |
| Impact | This is a genuine, actionable priority rather than a paper tiger. The vendor-assigned CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) shows a low-complexity network attack requiring only a low-privilege authenticated account (PR:L) with no user interaction, and the VC:H/SC:H metrics capture that a single flaw yields high confidentiality impact on both the CRM and a downstream system (the victim's mailbox). A public exploit path exists via the GitHub security advisory, raising real-world likelihood. However, the attacker must already be an authenticated EspoCRM user holding Email Account scope access and must know (or enumerate) a victim's Email Account record ID, which bounds this to insiders or attackers with a foothold rather than anonymous internet-wide exploitation. No EPSS score and no CISA KEV entry were provided, so there is no evidence of active exploitation - the signal is 'exploit code available, not known-exploited.' Net: credible, patch-worthy, but the authenticated prerequisite and lack of KEV place it below unauthenticated-RCE-tier emergencies. |
| Exploit ScenarioDerived | A low-privileged EspoCRM user who has been granted Email Account scope access authenticates, identifies or guesses a colleague's Email Account record ID, and requests that record through the PersonalAccount\Service endpoint. The response discloses the victim's stored IMAP password, which the attacker uses to log into the victim's mailbox directly. A public exploit/advisory describing this IDOR is available. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
EspoCRM deployments before 10.0.5 allow an authenticated user with Email Account scope to retrieve other users' stored IMAP passwords via an insecure direct object reference in PersonalAccount\Service, enabling mailbox compromise. Attackers must know or enumerate a victim's Email Account record ID, and publicly available exploit code exists; there is no confirmation of active exploitation (CISA KEV) at time of analysis. The vulnerability is a confidentiality-only issue with changed scope, rated high risk because it exposes reusable credentials.
RemediationAI
Upgrade to EspoCRM 10.0.5 or later (vendor-released patch: 10.0.5) as the primary fix, available via the vendor's GitHub security advisory GHSA-pj52-qx2q-4qfp at https://github.com/espocrm/espocrm/security/advisories/GHSA-pj52-qx2q-4qfp. If immediate upgrade is not possible, restrict the 'Email Account scope' permission to only fully trusted roles, audit role assignments for unnecessary scope grants, and rotate all stored IMAP passwords for accounts that may have been exposed; note that restricting scope can break legitimate email integration for users who rely on it, and password rotation will require reconfiguration of affected mail accounts. Additionally, monitor logs for anomalous requests to PersonalAccount\Service endpoints and review access to Email Account records, though such monitoring is detective rather than preventive. Because publicly available exploit code exists, prioritize patching internet-facing and multi-tenant EspoCRM instances where low-privilege accounts can be provisioned.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an insecure direct object reference (IDOR) in EspoCRM's PersonalAccount\Service, mapped to CWE-522 (Insufficiently Protected Credentials), which fails to bind authorization checks to the requested Email Account record ID before returning stored IMAP credentials. EspoCRM is a PHP-based CRM that integrates with mail servers, storing IMAP passwords for users' email accounts; the affected component is reachable by any authenticated user who holds the 'Email Account scope' permission. The CPE cpe:2.3:a:espocrm:espocrm:*:*:*:*:*:*:*:* covers all releases prior to the 10.0.5 fix, and the root cause is missing ownership validation on a sensitive credential field rather than a memory-safety or injection flaw. Exploitation yields cleartext IMAP passwords, which can be reused to read the victim's mailbox, and the changed scope (S:C) reflects that compromise of one user's credentials can affect resources outside the vulnerable component's security authority.
Know when Espocrm gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Authenticated low-priv user (PR:L) over the network (AV:N) with no UI; stolen IMAP creds grant access to a separate mailbox system, so S:C with C:H and no integrity/availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
EspoCRM before 10.0.5 contains an insecure direct object reference vulnerability in PersonalAccount\Service that allows users with Email Account scope access to retrieve other users' IMAP passwords. Attackers who know a victim's Email Account record ID can request that record to steal stored IMAP credentials and access the victim's mailbox.
Technical POC Analysis
Evidence basis: GitHub advisory GHSA-pj52-qx2q-4qfp only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 public PoC link from github
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
EspoCRM deployments older than 10.0.5 expose stored IMAP mailbox passwords belonging to other users to anyone holding an account with Email Account scope, meaning one compromised or low-trust CRM user could quietly collect credentials for multiple mailboxes across the organization. Because these passwords are reusable outside the CRM, the exposure reaches directly into corporate email, where business email compromise, invoice fraud, and unauthorized data access typically begin. Leadership should treat this as a credential-compromise event rather than an application bug, since remediation requires rotating secrets at the mail provider and not just patching software.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict and review Email Account scope assignments to trusted staff only; disable personal email account integration for non-essential users; isolate the EspoCRM administrative and integration interfaces behind network allow-listing or VPN; rotate all IMAP credentials stored in the platform and at the upstream mail providers; enforce multi-factor authentication on integrated mailboxes; enable and monitor audit logging for Email Account record access to detect enumeration or bulk retrieval.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Directory traversal vulnerability in EspoCRM before 2.6.0 allows remote attackers to include and execute arbitrary local
Path traversal in EspoCRM's formula scripting engine allows authenticated administrators to achieve arbitrary file read/
PHP object deserialization in EspoCRM versions prior to 9.3.7 lets an authenticated administrator achieve remote code ex
EspoCRM version 7.1.8 is vulnerable to Unrestricted File Upload allowing attackers to upload malicious file with any ext
EspoCRM 5.6.4 is vulnerable to user password hash enumeration. Rated high severity (CVSS 8.8), this vulnerability is rem
Authorization bypass in EspoCRM 5.8.5 lets an authenticated low-privilege user reuse or manipulate Basic-Authorization a
CSV Injection in Create Contacts in EspoCRM 7.1.8 allows remote authenticated users to run system commands via creating
Boolean-based blind SQL injection in EspoCRM versions 8.1.0 through 9.3.7 allows an authenticated non-administrator to i
Path traversal in EspoCRM admin template management allows authenticated administrators to read, create, overwrite, or d
Server-side request forgery in EspoCRM before 10.0.4 allows authenticated users to route outbound HTTP requests to inter
Stored cross-site scripting in EspoCRM 9.3.3 and below enables an authenticated attacker to execute arbitrary JavaScript
Information disclosure in EspoCRM's portal Note API allows an authenticated portal user (CVSS PR:L) who already has stre
Exploit-DB