CVE-2026-61460

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jul 10, 2026
No fix on record yet. Sources: github_pr.
Web page

Krayin CRM Insecure Direct Object Reference via Controllers | Advisories | VulnCheck

https://www.vulncheck.com/advisories/krayin-crm-insecure-direct-object-reference-via-controllers
GitHub pull request

fix issue#2559

Upstream fix in progress (PR #2567 · krayin/laravel-crm, state=open)

https://github.com/krayin/laravel-crm/pull/2567
Web page

Systematic 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/2559

Vendor 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 10× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 224 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:34 UTCEG score recompute
  2. 2026-10-11 16:49 UTCEG score recompute
  3. 2026-10-11 14:11 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-01 15:07 UTCEG score recompute
  16. 2026-10-01 15:07 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-09-28 09:47 UTCEG score recompute
  20. 2026-09-28 09:47 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-24 11:10 UTCEG score recompute
  23. 2026-09-24 11:10 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-09-23 05:45 UTCEG score recompute
Show 75 more
  1. 2026-09-23 05:45 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-09-18 05:18 UTCEG score recompute
  5. 2026-09-18 05:18 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-09-13 23:39 UTCEG score recompute
  9. 2026-09-13 23:39 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-09-13 08:12 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-09-12 15:29 UTCEG score recompute
  12. 2026-09-12 15:29 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-09-12 02:54 UTCEG score recompute
  14. 2026-09-12 02:54 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-09-08 02:50 UTCEG score recompute
  20. 2026-09-08 02:50 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-09-06 13:57 UTCEG score recompute
  23. 2026-09-06 13:57 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-09-05 21:41 UTCEG score recompute
  26. 2026-09-05 21:41 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  27. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  29. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-08-30 18:55 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-08-30 06:23 UTCEG score recompute
  34. 2026-08-30 06:23 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  36. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-08-27 21:40 UTCEG score recompute
  38. 2026-08-27 21:40 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-08-27 00:47 UTCEG score recompute
  41. 2026-08-27 00:47 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  42. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-08-26 03:36 UTCEG score recompute
  44. 2026-08-26 03:35 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  45. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  46. 2026-08-25 11:08 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  47. 2026-08-24 21:59 UTCEG score recompute
  48. 2026-08-24 21:59 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  49. 2026-08-24 09:27 UTCEG score recompute
  50. 2026-08-24 09:27 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  51. 2026-08-23 18:52 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  52. 2026-08-23 06:21 UTCEG score recompute
  53. 2026-08-23 06:21 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  54. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  55. 2026-08-22 17:49 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-08-22 05:16 UTCEG score recompute
  57. 2026-08-22 05:16 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  59. 2026-08-21 16:42 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-08-21 03:44 UTCEG score recompute
  61. 2026-08-21 03:44 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  62. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  63. 2026-08-20 15:12 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  64. 2026-08-20 01:32 UTCEG score recompute
  65. 2026-08-20 01:32 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  67. 2026-08-19 09:16 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  68. 2026-08-18 20:35 UTCEG score recompute
  69. 2026-08-18 20:35 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  70. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  71. 2026-08-18 04:24 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-08-17 15:44 UTCEG score recompute
  73. 2026-08-17 15:44 UTCGHSA enrichmentGHSA-9qgj-r9fj-454p · GitHub severity HIGH · GitHub CVSS 8.8
  74. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  75. 2026-08-17 03:13 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61460?
CVE-2026-61460 is a high-severity vulnerability; its CVE record was published on July 10, 2026. 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…
When was CVE-2026-61460 made public?
CVE-2026-61460 was made public on June 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 10, 2026. EchelonGraph's copy of the record carries a last-modified date of July 10, 2026; the record at its source may have been updated since.
Is CVE-2026-61460 actively exploited?
CVE-2026-61460 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61460?
CVE-2026-61460 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61460?
No fix for CVE-2026-61460 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-61460 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61460

Explore →

Is Your Infrastructure Affected by CVE-2026-61460?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs