CVE-2026-76901: CWE-639: Authorization Bypass Through User-Controlled Key in 1Panel-dev CordysCRM
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.
AI Analysis
Technical Summary
CordysCRM versions before 1.7.4 have an authorization bypass vulnerability (CWE-639) in the PoolClueController.get and PoolCustomerController.get endpoints. These endpoints perform permission checks for pool-read access but do not bind the CsPermission resourceId to enforce per-record data scope. As a result, an authenticated user with CLUE_MANAGEMENT_POOL:READ or CUSTOMER_MANAGEMENT_POOL:READ permissions can supply another record's ID and retrieve leads or accounts owned by other users, departments, or organizations. The exposed information includes contact names, phone numbers, owner and department attribution, and custom field values. The vulnerability is fixed in version 1.7.4.
Potential Impact
An authenticated user with read permissions can access sensitive data of leads and accounts that they should not have access to, including contact details and ownership information. This could lead to unauthorized disclosure of personal and organizational data. The vulnerability does not affect integrity or availability but compromises confidentiality.
Mitigation Recommendations
Upgrade CordysCRM to version 1.7.4 or later, where this authorization bypass vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
CVE-2026-76901: CWE-639: Authorization Bypass Through User-Controlled Key in 1Panel-dev CordysCRM
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.
CVSS v3.1
Score 5.8medium
Affected software
1Panel-dev
CordysCRM
pkg:github/1panel-dev/CordysCRMRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CordysCRM versions before 1.7.4 have an authorization bypass vulnerability (CWE-639) in the PoolClueController.get and PoolCustomerController.get endpoints. These endpoints perform permission checks for pool-read access but do not bind the CsPermission resourceId to enforce per-record data scope. As a result, an authenticated user with CLUE_MANAGEMENT_POOL:READ or CUSTOMER_MANAGEMENT_POOL:READ permissions can supply another record's ID and retrieve leads or accounts owned by other users, departments, or organizations. The exposed information includes contact names, phone numbers, owner and department attribution, and custom field values. The vulnerability is fixed in version 1.7.4.
Potential Impact
An authenticated user with read permissions can access sensitive data of leads and accounts that they should not have access to, including contact details and ownership information. This could lead to unauthorized disclosure of personal and organizational data. The vulnerability does not affect integrity or availability but compromises confidentiality.
Mitigation Recommendations
Upgrade CordysCRM to version 1.7.4 or later, where this authorization bypass vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-19T22:43:14.890Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aad98c155bf5e2cf57b8885
Added to database: 09/18/2026, 20:02:09 UTC
Last enriched: 09/18/2026, 20:32:21 UTC
Last updated: 09/19/2026, 00:49:48 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.