# CVE-2026-61460: Krayin CRM IDOR in multiple controllers

Source: https://junglewise.ai/threats/cve-2026-61460-krayin-crm-idor-in-multiple-controllers  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-10. Updated: 2026-07-10  
License: CC BY 4.0 with a link back

CVE-2026-61460 · Severity: high · CVSS 8.8 · Published 2026-07-10

Krayin CRM, an open-source customer relationship management platform, contains a security flaw that allows any logged-in user to view, modify, or delete records belonging to other users. This includes sensitive business data such as leads, contact information, organizational details, and quotes. An attacker could use this to disrupt business operations, steal customer data, or reassign ownership of sales opportunities to themselves.

## Quick answers

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

**How severe is CVE-2026-61460?** High severity, with a CVSS score of 8.8, published 10 July 2026.

**Which products and versions are affected?** Krayin Krayin CRM through 2.2.3.

**Is there a fix for CVE-2026-61460?** A patch was published on 2026-07-06: Fix proposed in GitHub pull request 2567 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-61460 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-61460?** Check whether anything you run is named in the advisory. 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.

## Technical details

An Insecure Direct Object Reference (IDOR) vulnerability exists in Krayin CRM through version 2.2.3 due to missing record-level ownership validation. The flaw is located within the edit, update, and destroy methods of several controllers, including LeadController, PersonController, OrganizationController, QuoteController, and ActivityController. An authenticated attacker can exploit this by manipulating object identifiers in network requests to access or modify CRM records they do not own. This allows for unauthorized data modification, deletion, and ownership reassignment. A patch has been proposed in the project's GitHub repository to implement proper authorization checks.

## Affected products

- Krayin Krayin CRM through 2.2.3

## Timeline

- 2026-07-06: patched: Fix proposed in GitHub pull request 2567
- 2026-07-10: disclosed: Initial disclosure and NVD publication

## References

- [https://github.com/krayin/laravel-crm/issues/2559](https://github.com/krayin/laravel-crm/issues/2559)
- [https://github.com/krayin/laravel-crm/pull/2567](https://github.com/krayin/laravel-crm/pull/2567)
- [https://www.vulncheck.com/advisories/krayin-crm-insecure-direct-object-reference-via-controllers](https://www.vulncheck.com/advisories/krayin-crm-insecure-direct-object-reference-via-controllers)