{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76900 exists.","fix":"No fix has been published for CVE-2026-76900 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76900 is a medium-severity server-side request forgery 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-76900 and fix it if it is affected.\n\nWhat it is: CVE-2026-76900 is a medium-severity server-side request forgery 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76900 exists.\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-76900/ (Markdown: https://insights.sbomify.com/CVE-2026-76900/index.md)","id":"CVE-2026-76900","markdown":"https://insights.sbomify.com/CVE-2026-76900/index.md","name":"CVE-2026-76900","record":{"aliases":["GHSA-fg6q-pfj7-fghw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"CordysCRM","requires_auth":"high_privilege","summary":"An attacker with process setting permissions can configure malicious webhooks to trigger server-side requests, enabling internal network access and metadata theft.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. In version 1.7.3, ApprovalResourceService.sendWebHook reads WebHookConfig.webHookUrl from stored approval-node configuration and passes it through ApprovalFlowService.updateApprovalPostField to HttpClientUtils without the SSRF validation used by the optional testConnect path. A user with PROCESS_SETTING_ADD can configure an internal URL through POST /approval-flow/add and cause the server to request it when POST /approval-action/approve executes the approval action, enabling cloud metadata access, internal network reconnaissance, and interaction with reachable internal services. 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":"weaponised"},"has_fix":false,"headline":"CordysCRM: SSRF via Approval Flow Webhook Execution due to Missing SSRF Validation at Runtime","id":"CVE-2026-76900","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in CordysCRM","id":"CVE-2026-76901"},"packages":[],"prev":{"headline":"CordysCRM: Authenticated SQL injection via `sort.name` on `POST /account-pool/page`","id":"CVE-2026-76899"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["1Panel-dev"]},"summary":"An attacker with process setting permissions can configure malicious webhooks to trigger server-side requests, enabling internal network access and metadata theft.","url":"https://insights.sbomify.com/CVE-2026-76900/"}