CVE-2026-76901

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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, secondary
Trending — 3 sources updated this week
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: None knownExposed: 0

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

CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. Prior to 1.7.4, GET /pool/lead/get/{id} in PoolClueController.get and GET /pool/account/get/{id} in PoolCustomerController.get use bare pool-read permission checks without the CsPermission resourceId binding that enforces per-record data scope. An authenticated user with the ordinary CLUE_MANAGEMENT_POOL:READ or CUSTOMER_MANAGEMENT_POOL:READ permission can supply another record's id and cause unscoped primary-key getters to return leads or accounts owned by other users, departments, or organizations. Exposed data includes contact names, phone numbers, owner and department attribution, and custom field values. This issue is fixed in version 1.7.4.

CVSS v3
5.8
EG Score
5.8(medium)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity58% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.7.4

Patch available: 1Panel-dev/CordysCRM v1.7.4

https://github.com/1Panel-dev/CordysCRM/releases/tag/v1.7.4
github_commit Patch Available

commit 34c7c3e5de25 (1Panel-dev/CordysCRM)

Patch available: 1Panel-dev/CordysCRM v1.7.4 (contains commit 34c7c3e5de25)

https://github.com/1Panel-dev/CordysCRM/commit/34c7c3e5de2585208744926007530037a4ce4da5
github_pr Patch Available

fix: customer pool and clue pool permission check

Patch available: 1Panel-dev/CordysCRM v1.7.4 (PR #2976 merged 2026-07-09)

https://github.com/1Panel-dev/CordysCRM/pull/2976
github Patch Available🟡 PoC Available

Broken object-level authorization in lead pool and account pool detail endpoints exposes arbitrary leads and accounts · Advisory · 1Panel-dev/CordysCRM · GitHub

https://github.com/1Panel-dev/CordysCRM/security/advisories/GHSA-hxp2-5w5p-2grq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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-09-20 23:30 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-19 22:00 UTCEG score recompute
  4. 2026-09-18 20:30 UTCEG score recompute
  5. 2026-09-18 19:59 UTCEG score recompute
  6. 2026-09-18 19:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76901?
CVE-2026-76901 is a medium vulnerability published on September 18, 2026. CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. Prior to 1.7.4, GET /pool/lead/get/{id} in PoolClueController.get and GET /pool/account/get/{id} in PoolCustomerController.get use bare pool-read permission checks without the…
When was CVE-2026-76901 disclosed?
CVE-2026-76901 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76901 actively exploited?
CVE-2026-76901 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-76901?
CVE-2026-76901 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-76901?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76901, 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-76901

Explore →

Is Your Infrastructure Affected by CVE-2026-76901?

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