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.
CVE-2026-61460
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EPSS
- 19.9%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (3)
Auto-updated Jul 10, 2026Krayin CRM Insecure Direct Object Reference via Controllers | Advisories | VulnCheck
https://www.vulncheck.com/advisories/krayin-crm-insecure-direct-object-reference-via-controllersfix issue#2559
Upstream fix in progress (PR #2567 · krayin/laravel-crm, state=open)
https://github.com/krayin/laravel-crm/pull/2567Systematic IDOR allows any agent to edit/update/delete records owned by other users · Issue #2559 · krayin/laravel-crm · GitHub
https://github.com/krayin/laravel-crm/issues/2559Vendor Advisories for CVE-2026-61460(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 09:38 UTCEG score recompute
- 2026-07-13 09:38 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 21:06 UTCEG score recompute
- 2026-07-12 21:05 UTCGHSA enrichment
- 2026-07-12 08:34 UTCEG score recompute
- 2026-07-12 08:33 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 20:01 UTCEG score recompute
- 2026-07-11 20:01 UTCGHSA enrichment
- 2026-07-11 07:30 UTCEG score recompute
- 2026-07-11 07:30 UTCGHSA enrichment
- 2026-07-10 18:59 UTCEG score recompute
- 2026-07-10 18:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-61460?
When was CVE-2026-61460 disclosed?
Is CVE-2026-61460 actively exploited?
What is the CVSS score of CVE-2026-61460?
How do I remediate CVE-2026-61460?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61460
Is Your Infrastructure Affected by CVE-2026-61460?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.