krayin laravel-crm up to 2.2.3 Record Management Controllers resource injection

Summaryinfo

A vulnerability has been found in krayin laravel-crm up to 2.2.3 and classified as critical. Affected by this vulnerability is an unknown functionality of the component Record Management Controllers. The manipulation leads to resource injection. This vulnerability is uniquely identified as CVE-2026-61460. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, has been found in krayin laravel-crm up to 2.2.3. This issue affects an unknown part of the component Record Management Controllers. The manipulation with an unknown input leads to a resource injection vulnerability. Using CWE to declare the problem leads to CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Krayin CRM through 2.2.3 contains an insecure direct object reference vulnerability in LeadController, PersonController, OrganizationController, QuoteController, and ActivityController that allows authenticated users to edit, update, or delete records owned by other users. Attackers can modify CRM records and reassign ownership by exploiting missing record-level ownership validation in edit, update, and destroy methods.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-61460 since 07/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/10/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Customer Relationship Management System

Vendor

• krayin

Name

• laravel-crm

Version

• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3

Website

• Product: https://github.com/krayin/laravel-crm/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion