Skip to main content
VulnerabilityPublished Updated

CVE-2026-76901: 1Panel-dev CordysCRM · Insecure Direct Object Reference

Affects 1Panel-dev CordysCRMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.8 Medium : upgrade to 1.7.4 when convenient.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.4
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade CordysCRM and 1panel-dev/CordysCRM to 1.7.4.

Affected software

ProductAffectedFixed in
1Panel-devCordysCRMAffected
  • <1.7.4
Fixed in
  • 1.7.4
GitHub1panel-dev/CordysCRMpkg:github/1panel-dev/CordysCRMOther threatsAffected
  • <1.7.4
Fixed in
  • 1.7.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade CordysCRM to version 1.7.4 or later where this authorization bypass vulnerability is fixed. No other mitigation is indicated or required.

Description

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.

References

Community reviews

Loading reviews…