# CVE-2026-41141: EspoCRM: IDOR in EmailTemplate Prepare Endpoint Leaks Entity Data via Email Address Lookup

> Authenticated users can bypass ACL restrictions to read sensitive entity data in EspoCRM by exploiting an IDOR vulnerability in the email template preparation endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-vvmh-mf4h-96hw

## What is CVE-2026-41141?

CVE-2026-41141 is a medium-severity missing authorization vulnerability in espocrm, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EspoCRM is an open source customer relationship management application. Prior to 9.3.5, the POST /api/v1/EmailTemplate/:id/prepare endpoint accepts an emailAddress parameter and resolves the owning entity (Contact, Lead, Account, or User) without performing an ACL check. An authenticated user with EmailTemplate read permission can extract all field values of any entity by supplying the target's email address, bypassing read: own or read: team ACL restrictions. This vulnerability is fixed in 9.3.5.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-41141?


## How do I fix CVE-2026-41141?

No fix has been published for CVE-2026-41141 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41141 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41141 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41141 and fix it if it is affected.

What it is: CVE-2026-41141 is a medium-severity missing authorization vulnerability in espocrm, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41141 exists.

Affected product: espocrm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41141/ (Markdown: https://insights.sbomify.com/CVE-2026-41141/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41141
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41141
- OSV: https://osv.dev/vulnerability/CVE-2026-41141

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41141/
Summaries are generated and may contain mistakes; the official description above is the record.