{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76901 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76901 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76901 is a medium-severity missing authorization vulnerability in 1Panel-dev CordysCRM, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76901 and fix it if it is affected.\n\nWhat it is: CVE-2026-76901 is a medium-severity missing authorization vulnerability in 1Panel-dev CordysCRM, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76901 in the wild and no public exploit code.\n\nAffected product: 1Panel-dev CordysCRM. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76901/ (Markdown: https://insights.sbomify.com/CVE-2026-76901/index.md)","id":"CVE-2026-76901","markdown":"https://insights.sbomify.com/CVE-2026-76901/index.md","name":"CVE-2026-76901","record":{"aliases":["GHSA-hxp2-5w5p-2grq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"CordysCRM","requires_auth":"high_privilege","summary":"Authenticated users can access arbitrary leads and accounts belonging to other users due to missing object-level authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing authorization in CordysCRM","id":"CVE-2026-76901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"CordysCRM: Unauthenticated arbitrary file disclosure via `/attachment/preview/{id}` and `/pic/preview/{id}`","id":"CVE-2026-76902"},"packages":[],"prev":{"headline":"CordysCRM: SSRF via Approval Flow Webhook Execution due to Missing SSRF Validation at Runtime","id":"CVE-2026-76900"},"products":["CordysCRM"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["1Panel-dev"]},"summary":"Authenticated users can access arbitrary leads and accounts belonging to other users due to missing object-level authorization checks.","url":"https://insights.sbomify.com/CVE-2026-76901/"}