CVE-2026-41453

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-03. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

Krayin CRM before 2.2.4 contains a blind SQL injection vulnerability in the leads DataGrid that allows authenticated users with leads access to inject arbitrary SQL into a HAVING clause by manipulating the rotten_lead[in] query parameter, which is concatenated without parameterized binding directly into a havingRaw() call in LeadDataGrid.php. Attackers can exploit this flaw using time-based and boolean-based blind injection techniques to extract the entire database contents, including user credential hashes, CRM records, and application configuration data.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 14, 2026

Advisory Details (4)

Auto-updated Aug 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github_commit.
generic

Krayin CRM < 2.2.4 Blind SQL Injection via LeadDataGrid.php rotten_lead Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/krayin-crm-blind-sql-injection-via-leaddatagrid-php-rotten-lead-parameter
github_commit Patch Available

commit 2a3724cb7e9e (krayin/laravel-crm)

Patch available: krayin/laravel-crm v2.2.4 (contains commit 2a3724cb7e9e)

https://github.com/krayin/laravel-crm/commit/2a3724cb7e9e65ab98f2b42c8ca2c98dede48f62
github_release Patch Available

v2.2.4

Patch available: krayin/laravel-crm v2.2.4

https://github.com/krayin/laravel-crm/releases/tag/v2.2.4
generic🟡 PoC Available

From Zero to Database Dump: Blind SQL Injection in Krayin CRM 2.2.0 (CVE-2026-41453) — Jiva Security

https://jivasecurity.com/writeups/krayin-lead-datagrid-sqli-cve-2026-41453

Vendor Advisories for CVE-2026-41453(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 28× in last 7d / 73× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:32 UTCGHSA enrichment
  3. 2026-08-20 09:15 UTCGHSA enrichment
  4. 2026-08-19 20:57 UTCEG score recompute
  5. 2026-08-19 20:57 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 08:36 UTCGHSA enrichment
  8. 2026-08-18 20:21 UTCEG score recompute
  9. 2026-08-18 20:21 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 07:53 UTCGHSA enrichment
  12. 2026-08-17 19:36 UTCEG score recompute
  13. 2026-08-17 19:36 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:34 UTCGHSA enrichment
  16. 2026-08-16 18:14 UTCEG score recompute
  17. 2026-08-16 18:14 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 05:58 UTCEG score recompute
  20. 2026-08-16 05:58 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 17:43 UTCGHSA enrichment
  23. 2026-08-15 05:27 UTCEG score recompute
  24. 2026-08-15 05:27 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 48 more
  1. 2026-08-14 17:11 UTCEG score recompute
  2. 2026-08-14 17:11 UTCGHSA enrichment
  3. 2026-08-14 12:52 UTCGHSA enrichment
  4. 2026-08-14 00:37 UTCEG score recompute
  5. 2026-08-14 00:37 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 12:21 UTCGHSA enrichment
  8. 2026-08-13 00:05 UTCEG score recompute
  9. 2026-08-13 00:05 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 11:50 UTCGHSA enrichment
  12. 2026-08-11 23:34 UTCEG score recompute
  13. 2026-08-11 23:34 UTCGHSA enrichment
  14. 2026-08-11 13:43 UTCEPSS rescore
  15. 2026-08-11 11:18 UTCEG score recompute
  16. 2026-08-11 11:18 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 23:02 UTCGHSA enrichment
  19. 2026-08-10 10:46 UTCGHSA enrichment
  20. 2026-08-09 22:31 UTCEG score recompute
  21. 2026-08-09 22:31 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 10:15 UTCGHSA enrichment
  24. 2026-08-08 22:00 UTCEG score recompute
  25. 2026-08-08 22:00 UTCGHSA enrichment
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 09:44 UTCGHSA enrichment
  28. 2026-08-07 21:29 UTCEG score recompute
  29. 2026-08-07 21:29 UTCGHSA enrichment
  30. 2026-08-07 09:13 UTCGHSA enrichment
  31. 2026-08-06 20:57 UTCEG score recompute
  32. 2026-08-06 20:57 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 08:41 UTCGHSA enrichment
  35. 2026-08-05 20:25 UTCEG score recompute
  36. 2026-08-05 20:25 UTCGHSA enrichment
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-05 08:09 UTCGHSA enrichment
  39. 2026-08-04 19:54 UTCEG score recompute
  40. 2026-08-04 19:54 UTCGHSA enrichment
  41. 2026-08-04 15:10 UTCEPSS rescore
  42. 2026-08-04 07:38 UTCGHSA enrichment
  43. 2026-08-03 19:18 UTCEG score recompute
  44. 2026-08-03 19:18 UTCGHSA enrichment
  45. 2026-08-03 18:23 UTCEG score recompute
  46. 2026-08-03 17:40 UTCEG score recompute
  47. 2026-08-03 16:19 UTCEG score recompute
  48. 2026-08-03 16:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-41453?
CVE-2026-41453 is a high vulnerability published on August 3, 2026. Krayin CRM before 2.2.4 contains a blind SQL injection vulnerability in the leads DataGrid that allows authenticated users with leads access to inject arbitrary SQL into a HAVING clause by manipulating the rotten_lead[in] query parameter, which is concatenated without parameterized binding directly…
When was CVE-2026-41453 disclosed?
CVE-2026-41453 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41453 actively exploited?
CVE-2026-41453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-41453?
CVE-2026-41453 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41453?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41453, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41453?

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