CVE-2026-33656
Path Traversal via Attachment sourceId in EspoCRM Formula Engine
Publication date: 2026-04-22
Last updated on: 2026-04-27
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| espocrm | espocrm | to 9.3.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in EspoCRM versions prior to 9.3.4. It involves the built-in formula scripting engine that allows an authenticated admin user to overwrite the sourceId field on Attachment entities.
Because the sourceId value is concatenated directly into a file path without any sanitization in the EspoUploadDir::getFilePath() function, an attacker can manipulate this to redirect file read or write operations to arbitrary paths within the web server's open_basedir scope.
This means an attacker with admin privileges can potentially access or modify files outside the intended directories, leading to serious security risks.
How can this vulnerability impact me? :
The vulnerability can have severe impacts including unauthorized reading or writing of files within the web server's allowed directory scope.
- Confidential data exposure by reading sensitive files.
- Data integrity compromise by overwriting or modifying files.
- Potential for further exploitation by manipulating files critical to the application or server.
Overall, it can lead to a complete compromise of confidentiality, integrity, and availability of the affected system.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade EspoCRM to version 9.3.4 or later, as this version fixes the issue.