---
id: CVE-2026-100883
title: A flaw has been found in Krayin laravel-crm up to 2.2.5
summary: >-
  A flaw has been found in Krayin laravel-crm up to 2.2.5. The affected element
  is an unknown function of the file packages/Webkul/Admin/src/Config/acl.php.
  Executing a manipulation can lead to improper access controls. The attack can
  be l…
severity: medium
cvss: 6.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'
cwe:
  - CWE-266
  - CWE-284
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
  - laravel-crm 2.2.5
published: '2026-09-27'
updated: '2026-09-27'
sourceUpdated: '2026-09-27T23:16:58.463'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100883'
references:
  - url: >-
      https://github.com/carlosalbertotuma/advisory/blob/main/advisory-05-Missing-Function-Level%20Authorization.md
    label: cna@vuldb.com
  - url: 'https://github.com/krayin/laravel-crm/'
    label: cna@vuldb.com
  - url: >-
      https://github.com/krayin/laravel-crm/commit/a399404a388d8ad2700a01349d0d98069c8e85a4
    label: cna@vuldb.com
  - url: 'https://github.com/krayin/laravel-crm/issues/2623'
    label: cna@vuldb.com
  - url: 'https://github.com/krayin/laravel-crm/pull/2626'
    label: cna@vuldb.com
  - url: 'https://github.com/krayin/laravel-crm/releases/tag/v2.2.6'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/cve/CVE-2026-100883'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/submit/916128'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/vuln/410813'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/vuln/410813/cti'
    label: cna@vuldb.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-27T22:59:18.881Z'
---

## Overview

A flaw has been found in Krayin laravel-crm up to 2.2.5. The affected element is an unknown function of the file packages/Webkul/Admin/src/Config/acl.php. Executing a manipulation can lead to improper access controls. The attack can be launched remotely. The exploit has been published and may be used. Upgrading to version 2.2.6 is sufficient to fix this issue. This patch is called a399404a388d8ad2700a01349d0d98069c8e85a4. The affected component should be upgraded.

## Remediation

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