Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 28 May 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 28 May 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Espocrm
Espocrm espocrm |
|
| Vendors & Products |
Espocrm
Espocrm espocrm |
Thu, 28 May 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | EspoCRM: Broken Access Control / IDOR in Note Pinning API allows unauthorized modification of notes | |
| Weaknesses | CWE-284 CWE-639 CWE-862 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-28T19:04:24.739Z
Reserved: 2026-04-17T16:34:45.524Z
Link: CVE-2026-41160
Updated: 2026-05-28T19:03:20.303Z
Status : Deferred
Published: 2026-05-28T17:16:22.053
Modified: 2026-05-28T20:16:23.507
Link: CVE-2026-41160
No data.
OpenCVE Enrichment
Updated: 2026-05-28T19:30:16Z