dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-61460

HIGH · 8.8 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Krayin CRM through 2.2.3 has an Insecure Direct Object Reference (IDOR) vulnerability in five controllers (LeadController, PersonController, OrganizationController, QuoteController, and ActivityController). The edit, update, and destroy methods lack record-level ownership validation, allowing authenticated users to modify, delete, or reassign CRM records belonging to other users.

MitigationImplement ownership validation checks in all edit, update, and destroy methods of the affected controllers to verify the authenticated user owns the record before allowing any modification or deletion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Krayin CRM installation
    Locate the Krayin CRM application by checking for composer.json in the web root directory or looking for the 'packages/Webkul/KrayinCrm' directory structure commonly found in Laravel-based CRM installations.
    Affected if Krayin CRM is not present on the system
  2. Determine the installed version
    Read the composer.json file in the web root and locate the 'krayin/crm' package version entry, or check the version file if one exists in the application root.
    Affected if The version is 2.2.3 or lower (any version through 2.2.3)
  3. Locate the affected controllers
    Search for the following controller files in the application: LeadController.php, PersonController.php, OrganizationController.php, QuoteController.php, and ActivityController.php, typically found under packages/Webkul/KrayinCrm/Http/Controllers/ or similar namespace paths.
    Affected if These five controller files exist in the installation
  4. Verify absence of ownership validation in edit/update/destroy methods
    Open each of the five controllers and inspect the edit, update, and destroy methods for any code that checks if the authenticated user owns the record before allowing modification or deletion. Look for statements that validate record ownership or user permissions.
    Affected if The edit, update, and destroy methods contain no ownership or permission validation checks before allowing operations on records
  5. Confirm multi-user environment is in use
    Check if the CRM has multiple user accounts configured by examining the users table or attempting to add a second user through the admin panel. Also verify that the application handles leads, persons, organizations, quotes, or activities that could be shared between users.
    Affected if Multiple users exist in the system and records can potentially be shared or reassigned between different user accounts

A user is affected if Krayin CRM version 2.2.3 or lower is installed, the five vulnerable controllers are present, and the edit/update/destroy methods lack ownership validation checks in a multi-user environment where records can be accessed across users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Implement ownership validation checks in all edit, update, and destroy methods of the affected controllers to verify the authenticated user owns the record before allowing any modification or deletion.

Recommended fix Moderate confidence

Version newer than 2.2.3 (the fix is in PR #2567)

  1. Review the changes in the vendor patch at https://github.com/krayin/laravel-crm/pull/2567 to understand the ownership validation fixes applied to LeadController, PersonController, OrganizationController, QuoteController, and ActivityController
  2. Identify the current Krayin CRM version in use
  3. Upgrade to a version newer than 2.2.3 that includes the fix from PR #2567
  4. After upgrade, verify that record-level ownership validation is properly enforced in the affected controllers
Caveat Review release notes for any breaking changes between current version and target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61460 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data