CVE-2026-41160 EspoCRM: Broken Access Control / IDOR in Note Pinning API allows unauthorized modification of notes
Low-privileged users can modify note pinning status in EspoCRM due to a broken access control flaw in the API.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-41160?
CVE-2026-41160 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, a business logic flaw (Broken Access Control) in EspoCRM 9.3.3 allows low-privileged users to pin arbitrary notes without having the required edit permissions for the parent object. Due to a "write first, authorize later" execution flaw in the backend API, even though the server correctly returns a 403 Forbidden error, the targeted note's pinned status is already persistently modified in the database. The root cause lies in the server-side processing of the POST /api/v1/Note/{id}/pin endpoint. In application/Espo/Tools/Stream/Api/PostNotePin.php, the process() method first calls getNote($id) before calling checkParent($note). This vulnerability is fixed in 9.3.5.
Which versions are affected by CVE-2026-41160?
How do I fix CVE-2026-41160?
No fix has been published for CVE-2026-41160 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-41160 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41160 exists.
Sources
Also known as GHSA-c3rm-m24p-255p.