# CVE-2026-125374: Krayin CRM broken object level authorization in Lead TagController

Source: https://junglewise.ai/threats/cve-2026-125374-krayin-crm-before-2-2-8-contains-a-broken-object-level  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-125374 · Severity: medium · CVSS 4.3 · Published 2026-11-10

Krayin CRM is an open-source customer relationship management platform for managing leads and sales. Authenticated users with restricted data access (e.g., limited to their own or their team's leads) can manipulate tags on leads belonging to other users, potentially exposing or miscategorizing sensitive customer data they should not access.

Technologies: [Krayin CRM](https://junglewise.ai/threats/technologies/krayin-crm-1). Vendors: [Krayin](https://junglewise.ai/threats/vendors/krayin).

## Quick answers

**Is CVE-2026-125374 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-125374 being exploited in the wild.

**How severe is CVE-2026-125374?** Medium severity, with a CVSS score of 4.3, published 10 November 2026.

**Which products and versions are affected?** Krayin CRM before 2.2.8.

**Is there a fix for CVE-2026-125374?** Yes: fixed in 2.2.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-125374 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-125374?** Check whether you run Krayin CRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2.2.8

## Technical details

The Lead TagController's attach and detach methods bypass data-scope authorization checks, allowing authenticated users to add or remove tags on leads outside their assigned scope. An authenticated user with restricted permissions can exploit this by directly calling the attach or detach endpoints with a lead ID they would normally not have access to, bypassing authorization validation and modifying lead metadata across the entire system.

## Affected products

- Krayin CRM before 2.2.8

## References

- [https://github.com/krayin/laravel-crm](https://github.com/krayin/laravel-crm)
- [https://github.com/krayin/laravel-crm/blob/999b596d0f53cb11c9b029f733a1d67e01fccda6/packages/Webkul/Admin/src/Http/Controllers/Lead/TagController.php](https://github.com/krayin/laravel-crm/blob/999b596d0f53cb11c9b029f733a1d67e01fccda6/packages/Webkul/Admin/src/Http/Controllers/Lead/TagController.php)

## Related threats

- [Krayin CRM broken object-level authorization in EmailController](https://junglewise.ai/threats/cve-2026-112287-krayin-crm-before-2-2-7-contains-a-broken-object-level)
- [Krayin CRM insecure direct object reference in quote controller](https://junglewise.ai/threats/cve-2026-112286-krayin-crm-before-2-2-7-contains-an-insecure-direct-object)