CVE-2026-41160

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
4.3
EG Score
4.3(medium)
EPSS
21.1%
KEV
Not listed

Published

May 28, 2026

Last Modified

May 28, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Broken Access Control / IDOR in Note Pinning API allows unauthorized modification of notes · Advisory · espocrm/espocrm · GitHub

https://github.com/espocrm/espocrm/security/advisories/GHSA-c3rm-m24p-255p

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-16 02:54 UTCEG score recompute
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 19:51 UTCEG score recompute
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 18:07 UTCEG score recompute
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-02 12:54 UTCEG score recompute
  23. 2026-07-01 15:06 UTCEPSS rescore
  24. 2026-07-01 02:54 UTCEG score recompute
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 75 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 13:41 UTCEG score recompute
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 12:29 UTCEG score recompute
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 14:29 UTCEG score recompute
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-26 16:45 UTCEG score recompute
  9. 2026-06-25 14:19 UTCEG score recompute
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 16:36 UTCEG score recompute
  13. 2026-06-24 14:05 UTCEPSS rescore
  14. 2026-06-23 21:33 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 01:59 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-19 00:24 UTCEG score recompute
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-17 17:53 UTCEPSS rescore
  25. 2026-06-17 13:19 UTCEG score recompute
  26. 2026-06-16 17:52 UTCEPSS rescore
  27. 2026-06-16 15:37 UTCEG score recompute
  28. 2026-06-15 17:49 UTCEPSS rescore
  29. 2026-06-15 14:57 UTCEG score recompute
  30. 2026-06-14 17:14 UTCEG score recompute
  31. 2026-06-13 23:00 UTCEPSS rescore
  32. 2026-06-13 19:30 UTCEG score recompute
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 23:12 UTCEPSS rescore
  35. 2026-06-12 19:14 UTCEG score recompute
  36. 2026-06-11 21:32 UTCEG score recompute
  37. 2026-06-11 14:00 UTCEPSS rescore
  38. 2026-06-10 23:50 UTCEG score recompute
  39. 2026-06-10 22:18 UTCEPSS rescore
  40. 2026-06-10 13:22 UTCEPSS rescore
  41. 2026-06-10 13:22 UTCEPSS rescore
  42. 2026-06-10 02:08 UTCEG score recompute
  43. 2026-06-09 04:26 UTCEG score recompute
  44. 2026-06-08 14:17 UTCEPSS rescore
  45. 2026-06-08 14:17 UTCEPSS rescore
  46. 2026-06-08 06:43 UTCEG score recompute
  47. 2026-06-07 15:25 UTCEPSS rescore
  48. 2026-06-07 15:25 UTCEPSS rescore
  49. 2026-06-07 09:01 UTCEG score recompute
  50. 2026-06-06 13:47 UTCEPSS rescore
  51. 2026-06-06 13:47 UTCEPSS rescore
  52. 2026-06-06 11:20 UTCEG score recompute
  53. 2026-06-05 22:47 UTCEPSS rescore
  54. 2026-06-05 13:36 UTCEG score recompute
  55. 2026-06-05 06:10 UTCEPSS rescore
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-04 15:54 UTCEG score recompute
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-04 13:12 UTCEPSS rescore
  60. 2026-06-03 18:12 UTCEG score recompute
  61. 2026-06-02 20:30 UTCEG score recompute
  62. 2026-06-02 20:13 UTCEPSS rescore
  63. 2026-06-01 22:47 UTCEG score recompute
  64. 2026-06-01 13:52 UTCEPSS rescore
  65. 2026-06-01 13:52 UTCEPSS rescore
  66. 2026-06-01 13:51 UTCEPSS rescore
  67. 2026-06-01 01:05 UTCEG score recompute
  68. 2026-05-31 22:30 UTCEPSS rescore
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 00:16 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-31 00:16 UTCEPSS rescore
  73. 2026-05-29 13:44 UTCEPSS rescore
  74. 2026-05-29 13:44 UTCEPSS rescore
  75. 2026-05-28 16:47 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-41160?
CVE-2026-41160 is a medium vulnerability published on May 28, 2026. 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,…
When was CVE-2026-41160 disclosed?
CVE-2026-41160 was first published in the National Vulnerability Database on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41160 actively exploited?
CVE-2026-41160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41160?
CVE-2026-41160 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-41160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41160, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-41160

Explore →

Is Your Infrastructure Affected by CVE-2026-41160?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs