CVE-2026-33733
Path Traversal in EspoCRM Admin Template Allows Arbitrary File Access
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-23 | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that 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. The admin template management endpoints accept attacker-controlled 'name' and 'scope' values without proper normalization or filtering for directory traversal sequences like '../'. An authenticated admin can exploit this by using these sequences to escape the intended template directory and access files named 'body.tpl' or 'subject.tpl' anywhere in the web application user's filesystem.
This allows the attacker to read, create, overwrite, or delete arbitrary files within the permissions of the web application user.
The issue was fixed in version 9.3.4.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows an authenticated admin to manipulate critical template files arbitrarily.
- Reading sensitive files could lead to information disclosure.
- Creating or overwriting files could allow injection of malicious code or modification of application behavior.
- Deleting files could disrupt application functionality.
Overall, this can compromise the confidentiality, integrity, and availability of the application and its data.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade EspoCRM to version 9.3.4 or later, as this version fixes the issue.
Additionally, restrict admin access to trusted users only, since the vulnerability requires authenticated admin privileges.