Vulnerability in EspoCRM (CVE-2026-41160)
Summary
Vulnerability in EspoCRM (CVE-2026-41160). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1/Note/{id}/pin. Mitigation: upgrade to 9.3.5 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41160 has been found in EspoCRM.
Attackers can target a specific entry point like POST /api/v1/Note/{id}/pin over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade EspoCRM to 9.3.5 or later.
If unsure, ask your IT team or search "EspoCRM CVE-2026-41160" on the vendor's site.
CVE-2026-41160 (EspoCRM) — CWE-284 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/Note/{id}/pin
Patched: 9.3.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in EspoCRM. Attackers reach the vulnerable code path via POST /api/v1/Note/{id}/pin.
Check the vendor advisory for the affected versions of EspoCRM. Attack surface: POST /api/v1/Note/{id}/pin.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 9.3.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/Note/{id}/pin requests with malformed payloads or SQL meta-characters. Run grep -r 'EspoCRM' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'EspoCRM' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
EspoCRMを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v1/Note/{id}/pin' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/Note/{id}/pinへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade EspoCRM to 9.3.5ステージング環境で 9.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/Note/{id}/pin on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov