CVE-2026-38527
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceServer-Side Request Forgery (SSRF) vulnerability in the /settings/webhooks/create endpoint of Webkul Krayin CRM v2.2.x allows remote attackers to make the server perform requests to arbitrary URLs, enabling internal network scanning and potential access to internal services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Webkul Krayin CRM installationCheck your application for the presence of Krayin CRM files. Look for the composer.json file in the project root, or check the application banner/version endpoint if available.Affected if The application is not Webkul Krayin CRM
-
Identify installed Krayin CRM versionCheck the composer.json file or any version file in the application root for the version declaration. Compare against the v2.2.x range.Affected if The installed version is 2.2.x or within the 2.2.x range (e.g., 2.2.0 to 2.2.x)
-
Verify webhooks module is enabledCheck the application configuration or module registry to confirm the webhooks functionality is loaded and active.Affected if The webhooks module is enabled and accessible
-
Inspect webhook URL validation configurationExamine the webhook creation endpoint code or configuration files for URL validation logic. Look for any allowlist or validation mechanism in the webhooks configuration.Affected if No URL allowlist validation is configured, or validation can be bypassed
-
Check for internal network request blockingReview the webhook URL validation code or configuration to determine if there are checks to block requests to internal/private IP ranges (127.0.0.1, localhost, 10.x.x.x, 192.168.x.x, etc.).Affected if No IP range restrictions are implemented for webhook URLs
A user is affected if they are running Webkul Krayin CRM version 2.2.x with the webhooks module enabled and without proper URL allowlist or internal IP blocking validation in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict URL allowlist validation and deny-by-default for webhook URLs, with additional checks to block requests to internal/private IP ranges (localhost, 127.0.0.1, 10.x.x.x, 192.168.x.x, etc.).
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38527 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-38527 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data