/

CVE-2026-38527

Severity:

HIGH RISK

(8.5)

SSRF in Webkul Krayin CRM Webhook Creation

CVE-2026-38527

Deferred

Vulnerability type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Internal Network Scanning and Potential Pivoting via SSRF

Severity:

HIGH RISK

(8.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A Server-Side Request Forgery (SSRF) flaw in the /settings/webhooks/create component of Webkul Krayin CRM v2.2.x allows crafted POST requests to make the server initiate outbound HTTP requests to attacker-controlled targets.

When abused, this behavior can be used to scan internal network resources that are not directly accessible from the internet, potentially exposing internal services and metadata.

Affected context

The vulnerability appears in Krayin CRM deployments that expose the webhook creation endpoint and allow users to submit webhook target URLs.

It is most relevant in environments where the CRM server has network visibility into internal services (e.g., internal APIs, databases, cloud metadata endpoints) that are not directly exposed externally.

The risk increases when network egress from the CRM server is broadly permitted and when webhook URL validation or allowlisting is weak or absent.

Exploit preconditions

  • Attack surface: HTTP(S) interface for /settings/webhooks/create
  • Required access: Ability to send authenticated or unauthenticated POST requests to the webhook creation endpoint, depending on deployment configuration
  • Trigger point: Submitting a crafted webhook URL in the POST payload that points to internal or sensitive network locations
  • Why exploitation is possible: The server-side logic uses the user-supplied URL for outbound requests or validation without sufficiently restricting which hosts, IP ranges, or schemes can be targeted, enabling the server to act as a network proxy.

Why this happens

This issue stems from the classic Server-Side Request Forgery pattern, mapped to CWE-918.

The webhook creation feature accepts a user-supplied URL and allows the server to initiate outbound HTTP requests based on that value.

Without strict validation, allowlists, or network-level egress controls, attackers can coerce the application server into sending requests to internal or otherwise unreachable endpoints.

Conceptually, the bug is the absence of robust controls around where the server is allowed to connect, combined with treating user-controlled URLs as trusted destinations for server-side network calls.

Potential impact

  • Discovery and enumeration of internal HTTP-based services and open ports
  • Interaction with internal admin panels, APIs, or management interfaces not exposed to the internet
  • Access to cloud service metadata endpoints, which could expose credentials or configuration data
  • Use of the CRM server as a pivot point for further attacks against internal infrastructure
  • Increased difficulty of network monitoring and attribution, as malicious traffic appears to originate from the CRM host

General mitigation guidance

Mitigations should focus on constraining where server-side HTTP requests can go and reducing trust in user-controlled URLs:

  • Apply strict allowlisting of permitted webhook domains or hostnames, ideally limited to known external endpoints.
  • Block requests to internal IP ranges (e.g., RFC1918, link-local, loopback), cloud metadata addresses, and non-HTTP schemes at the application and/or network layers.
  • Normalize and re-parse user-supplied URLs server-side, resolving redirects carefully, and reject ambiguous or obfuscated URLs.
  • Introduce network egress controls (firewall rules, outbound proxies) that prevent the application server from reaching sensitive internal services directly.
  • Run the CRM with least-privilege network access, limiting its ability to communicate laterally within the infrastructure.

How teams detect issues like this

Detection efforts can combine code-level analysis with behavioral monitoring:

  • Use static analysis and code review to flag patterns where:
  • User-controlled URL parameters are passed directly into HTTP client libraries
  • Outbound HTTP clients lack host or IP validation logic
  • Review webhook-handling code for missing domain allowlists, IP range checks, or scheme restrictions.
  • Monitor outbound traffic from CRM servers for:
  • Requests to internal IP ranges, loopback addresses, or cloud metadata endpoints
  • Unusual spikes in outbound connections or port scanning-like patterns
  • Consider integrating automated security testing tools or SSRF-focused scanners into CI/CD pipelines to exercise webhook and URL-based features.

Sources

SourceLink
github.comgithub.com/TREXNEGRO/Security-Advisories/tree/main/CVE-2026-38527
github.comgithub.com/krayin/laravel-crm

Frequently asked

questions

Yes. If the /settings/webhooks/create endpoint is reachable by attackers, they can submit crafted POST requests to exploit the SSRF, subject to any authentication or access controls in place.

At minimum, an attacker needs the ability to reach and invoke the webhook creation endpoint.

In many deployments this may require an authenticated CRM account, but in misconfigured setups it could be accessible without authentication.

The safest approach is to enforce a strict allowlist of permitted webhook domains, block internal and special IP ranges, normalize and validate URLs server-side, and combine these checks with network-level egress controls to prevent access to sensitive internal resources.

Treat all user-supplied URLs as untrusted, centralize outbound HTTP logic behind a vetted client that enforces host/IP restrictions, subject webhook-like features to security review, and ensure that application servers have tightly controlled outbound network access by default.

Find out what's already
exploitable in your codebase.