---
id: CVE-2026-100885
title: A vulnerability was found in Krayin laravel-crm up to 2.2.4
summary: >-
  A vulnerability was found in Krayin laravel-crm up to 2.2.4. This affects an
  unknown function of the file
  packages/Webkul/Installer/src/Http/Middleware/CanInstall.php of the component
  admin-config-setup API Endpoint. The manipulation res…
severity: high
cvss: 7.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'
cwe:
  - CWE-285
  - CWE-639
vendor: Krayin
product: laravel-crm
affected:
  - laravel-crm 2.2.0
  - laravel-crm 2.2.1
  - laravel-crm 2.2.2
  - laravel-crm 2.2.3
  - laravel-crm 2.2.4
published: '2026-09-27'
updated: '2026-09-27'
sourceUpdated: '2026-09-27T23:16:58.843'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100885'
references:
  - url: >-
      https://github.com/carlosalbertotuma/advisory/blob/main/advisory-07-Unauthenticated-InstallerBypass.md
    label: cna@vuldb.com
  - url: 'https://github.com/krayin/laravel-crm/'
    label: cna@vuldb.com
  - url: >-
      https://github.com/krayin/laravel-crm/commit/89f2916b6a46ff91bd1999ce38158fa0de8b9490
    label: cna@vuldb.com
  - url: 'https://github.com/krayin/laravel-crm/pull/2614'
    label: cna@vuldb.com
  - url: 'https://github.com/krayin/laravel-crm/releases/tag/v2.2.5'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/cve/CVE-2026-100885'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/submit/916597'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/vuln/410815'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/vuln/410815/cti'
    label: cna@vuldb.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-27T22:59:18.879Z'
---

## Overview

A vulnerability was found in Krayin laravel-crm up to 2.2.4. This affects an unknown function of the file packages/Webkul/Installer/src/Http/Middleware/CanInstall.php of the component admin-config-setup API Endpoint. The manipulation results in authorization bypass. The attack may be launched remotely. The exploit has been made public and could be used. Upgrading to version 2.2.5 mitigates this issue. The patch is identified as 89f2916b6a46ff91bd1999ce38158fa0de8b9490. Upgrading the affected component is recommended.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.