Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-90944 – Unauthenticated Email Injection – Krayin CRM ≤ 2.2.6

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-90944 is an unauthenticated email injection vulnerability in Krayin CRM (Webkul’s Laravel-based CRM) affecting all versions through 2.2.6. The flaw allows an unauthenticated remote attacker to submit crafted RFC 2822 email messages to the CRM’s inbound mail-parsing endpoint, inserting fabricated emails with forged sender identities directly into the CRM inbox. The issue is rated HIGH severity and carries a CVSS v4.0 base score of 8.8.

Technical details

  • Root cause: the POST /admin/mail/inbound-parse route (used to ingest inbound email via the Sendgrid inbound-parse webhook driver) is exempted from CSRF protection and explicitly excludes authentication middleware (->withoutMiddleware('user')), and the application does not validate any webhook signature on the submitted email content.
  • Trigger condition: the Sendgrid inbound-mail receiver driver is the default MAIL_RECEIVER_DRIVER configuration, so the endpoint is reachable and exposed on a default installation.
  • Attack vector: network, no authentication or user interaction required. An attacker sends a crafted RFC 2822 message with forged sender/header information as the email parameter to the endpoint.
  • Impact: arbitrary emails — with any subject, body, and forged sender — can be injected into the CRM, including fabricated replies inserted into existing conversation threads. This enables phishing, spoofing of legitimate correspondence, and manipulation of the CRM’s communication/audit trail. The vulnerability affects data integrity (and to a lesser degree availability) rather than confidentiality.

Affected software

  • Webkul Krayin CRM (laravel-crm): all versions through 2.2.6 (version 0 up to and including 2.2.6)

Severity

  • CVSS v3.1 Base Score: 8.2 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
  • CVSS v4.0 Base Score: 8.8 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: No official patched version has been published at the time of writing; monitor the Krayin CRM GitHub repository and issue tracker (issue #2560) for a fix release and upgrade as soon as one is available.
  • If no patch is available: restrict network access to the /admin/mail/inbound-parse endpoint (e.g., allow-list the mail provider’s webhook source IPs at the network/firewall layer), disable or reconfigure the Sendgrid inbound-parse mail receiver driver if not actively required, and add signature/authentication verification in front of the endpoint. Monitor CRM inboxes for unexpected or suspicious injected messages and unusual reply-thread activity.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge