# CVE-2026-76900: CordysCRM: SSRF via Approval Flow Webhook Execution due to Missing SSRF Validation at Runtime

> An attacker with process setting permissions can configure malicious webhooks to trigger server-side requests, enabling internal network access and metadata theft.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-fg6q-pfj7-fghw

## What is CVE-2026-76900?

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.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-76900?


## How do I fix CVE-2026-76900?

No fix has been published for CVE-2026-76900 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76900 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76900 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76900 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76900 exists.

Affected product: 1Panel-dev CordysCRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76900/ (Markdown: https://insights.sbomify.com/CVE-2026-76900/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76900
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76900
- OSV: https://osv.dev/vulnerability/CVE-2026-76900

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76900/
Summaries are generated and may contain mistakes; the official description above is the record.