# CVE-2026-38527: Webkul Krayin CRM has Server-Side Request Forgery (SSRF)

> Attackers can scan internal resources via crafted POST requests in the webhook creation component of Krayin CRM.

- **Severity:** High 8.5 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/PR:L/S:C/UI: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:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-fpx9-9hq8-w2xc

## What is CVE-2026-38527?

CVE-2026-38527 is a high-severity server-side request forgery vulnerability in n/a, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) in the /settings/webhooks/create component of Webkul Krayin CRM v2.2.x allows attackers to scan internal resources via supplying a crafted POST request.

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

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

2 open source packages ship an affected version, including krayin/laravel-crm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krayin/laravel-crm` | Packagist | All versions to 2.2.0 | None |
| `krayin/laravel-crm` | Packagist | All versions to 2.2.0 | None |

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

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

## Is CVE-2026-38527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38527 is a high-severity server-side request forgery vulnerability in n/a, published on 14 Apr 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-38527 in the wild and no public exploit code.

Affected packages and fixed versions:
- krayin/laravel-crm (Packagist): affected all versions up to 2.2.0; no fix listed
- krayin/laravel-crm (Packagist): affected all versions up to 2.2.0; no fix listed

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-38527/ (Markdown: https://insights.sbomify.com/CVE-2026-38527/index.md)
```

## Sources

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

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