# CVE-2026-109958: EspoCRM 4.0.0 before 10.0.7 Field-Level Access Bypass via Address-Book Search

> Authenticated users can bypass field-level restrictions to read restricted email addresses via the address-book search API.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-2cr7-9g4f-8723, GHSA-98c7-3m9j-hm6f

## What is CVE-2026-109958?

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

### Official description

EspoCRM 4.0.0 before 10.0.7 contains an improper access control vulnerability that allows authenticated users to read restricted emailAddress values via the address-book search API. Users with record access can query address-book search to obtain email addresses even when Roles restrict the emailAddress field.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-109958 being exploited?

There is no known exploitation of CVE-2026-109958 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109958 is a medium-severity missing authorization vulnerability in espocrm, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109958 in the wild and no public exploit code.

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-109958/ (Markdown: https://insights.sbomify.com/CVE-2026-109958/index.md)
```

## Sources

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

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