# CVE-2026-67530: WACRM: SSRF via the automation `send_webhook` action

> Authenticated users can trigger server-side requests to internal or cloud metadata addresses via the automation webhook action, bypassing SSRF protections.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-8jqh-598v-rfxc

## What is CVE-2026-67530?

CVE-2026-67530 is a medium-severity server-side request forgery vulnerability in ArnasDon wacrm, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WACRM is a self-hostable CRM template for WhatsApp. In 0.7.0 and earlier, the automation send_webhook action in src/lib/automations/engine.ts and its validation in src/lib/automations/validate.ts allowed an authenticated user with automation privileges to submit an arbitrary webhook URL that the server fetched without the existing isDeliverableUrl SSRF guard in src/lib/webhooks/ssrf.ts, allowing requests to private, loopback, link-local, or cloud metadata addresses such as the cloud metadata endpoint at 169.254.169.254. This vulnerability is fixed with commit 23838a9959550e975d732ae08a44a3a2f0cc084b.

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

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


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

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

## Is CVE-2026-67530 being exploited?

There is no known exploitation of CVE-2026-67530 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67530 is a medium-severity server-side request forgery vulnerability in ArnasDon wacrm, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67530 in the wild and no public exploit code.

Affected product: ArnasDon wacrm. 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-67530/ (Markdown: https://insights.sbomify.com/CVE-2026-67530/index.md)
```

## Sources

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

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