CVE-2026-109957: EspoCRM insecure direct object reference in Import attachment handling

CVE-2026-109957 · Severity: medium · CVSS 4.3 · Published 2026-10-13

EspoCRM is a CRM (customer relationship management) system that allows businesses to manage customer data and interactions. An authenticated user with Import privileges can access and extract data from other users' file attachments by exploiting a flaw in the Import endpoint, then download the stolen data as a CSV file they control. This allows unauthorized disclosure of confidential business documents and customer information.

Technologies: Espocrm. Vendors: Espocrm.

Quick answers

Is CVE-2026-109957 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-109957 being exploited in the wild.
How severe is CVE-2026-109957?
Medium severity, with a CVSS score of 4.3, published 13 October 2026.
Which products and versions are affected?
Espocrm before 10.0.7.
Is there a fix for CVE-2026-109957?
Yes: fixed in 10.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-109957 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-109957?
Check whether you run Espocrm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 10.0.7

Technical details

An insecure direct object reference (IDOR) vulnerability exists in the POST /api/v1/Import endpoint, which accepts a caller-controlled attachmentId parameter without verifying authorization. An authenticated attacker with Import scope access can reference an attachment ID belonging to another user, and after creating an Import record, call the error export endpoint to copy the original attachment's data into a new CSV owned by the attacker. This requires knowledge of the target attachment ID and authentication to the system.

Affected products

  • EspoCRM EspoCRM before 10.0.7

Timeline

  • 2026-09-29: disclosed
  • 2026-10-13: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.