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

Back
New CVE Detected

CVE-2026-41452 – Pre-Authentication Admin Account Takeover – Krayin CRM (laravel-crm) ≤ 2.2.0 and 2.

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-41452 is a missing-authentication vulnerability (CWE-306) in the installer middleware of Krayin CRM (krayin/laravel-crm). An unauthenticated, network-based attacker can overwrite the primary administrator account with arbitrary credentials and obtain full administrative access to the application. It is rated Critical.

Technical details

  • Root cause: The CanInstall middleware exempts AJAX requests (those carrying the X-Requested-With: XMLHttpRequest header) from the "already installed" redirect, so installer endpoints remain reachable even after installation completes. The installer routes also use withoutMiddleware('web'), removing Laravel CSRF protection, and the adminConfigSetup() method updates the admin user record (user ID 1) directly from request input with no authentication check.
  • Trigger conditions: A POST request to /install/api/admin-config-setup including the header X-Requested-With: XMLHttpRequest, against an application that is already fully installed. No authentication and no CSRF token are required.
  • Attack vector: Network (remote, unauthenticated). The request body supplies attacker-chosen name, email, and password, which overwrite the administrator account via updateOrInsert().
  • Impact: Complete takeover of the administrator account, granting full administrative access to the CRM and its data.

Affected software

  • Krayin CRM (krayin/laravel-crm) versions 0 through 2.2.0.
  • Krayin CRM (krayin/laravel-crm) version 2.2.4 (an earlier fix was reverted).
  • Versions 2.2.1 through 2.2.3 are not affected.

Severity

  • CVSS v3.1 base score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 base score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to a fixed release once available (versions 2.2.1–2.2.3 contained the fix before it was reverted in 2.2.4); monitor the vendor repository for a re-applied patch and apply it.
  • If no patch: Remove the AJAX exception in the CanInstall middleware so the "already installed" check applies to all requests; remove the Installer package from production after setup; block /install/* at the reverse proxy; require authentication and restore CSRF protection on installer routes. Monitor for POST requests to /install/api/admin-config-setup and review administrator account changes.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Krayin CRM
  • Raw response body: /vendor/krayin/, /themes/krayin/
  • set-cookie response header: krayin_crm_session

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