Vulnerability 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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/espocrm/espocrm/security/advisories/GHSA-c3rm-m24p-255p
- https://github.com/espocrm/espocrm/security/advisories/GHSA-c3rm-m24p-255p
FAQ
What is CVE-2026-41160?
CVE-2026-41160 is a vulnerability with a CVSS score of 4.3 (MEDIUM). 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 note...
How severe is CVE-2026-41160?
CVE-2026-41160 has been rated MEDIUM with a CVSS base score of 4.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-41160?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.