CVE-2026-38532

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-04-14. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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

A Broken Object-Level Authorization (BOLA) in the /Contact/Persons/PersonController.php endpoint of Webkul Krayin CRM v2.2.x allows authenticated attackers to arbitrarily read, modify, and permanently delete any contact owned by other users via supplying a crafted GET request.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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 within your standard update timelines, and watch for a fix.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation none (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

April 14, 2026

Last Modified

April 23, 2026

Advisory Details (2)

Auto-updated May 5, 2026
No fix on record yet.
Web page

GitHub - krayin/laravel-crm: Free & Opensource Laravel CRM solution for SMEs and Enterprises for complete customer lifecycle management. · GitHub

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

Security-Advisories/CVE-2026-38532 at main · TREXNEGRO/Security-Advisories · GitHub

https://github.com/TREXNEGRO/Security-Advisories/tree/main/CVE-2026-38532

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerkrayin/laravel-crm—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
krayin/laravel-crmv1.0.0 ... v2.2.0 (28 versions)
  • every version through 2.2.0: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 29× 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 99 of 216 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-38532?
CVE-2026-38532 is a high-severity vulnerability; its CVE record was published on April 14, 2026. A Broken Object-Level Authorization (BOLA) in the /Contact/Persons/PersonController.php endpoint of Webkul Krayin CRM v2.2.x allows authenticated attackers to arbitrarily read, modify, and permanently delete any contact owned by other users via supplying a crafted GET request.
When was the CVE record for CVE-2026-38532 published?
The CVE record for CVE-2026-38532 was published on April 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2026-38532 actively exploited?
CVE-2026-38532 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-38532?
CVE-2026-38532 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-38532?
No fix for CVE-2026-38532 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-38532

Explore →

Is Your Infrastructure Affected by CVE-2026-38532?

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

Book a Demo →Browse All CVEs