Skip to content
Applications

CVE-2026-41453

HIGH
High
EPSS 0.35%Patch availableAug 4, 2026

Authenticated blind SQL injection in Krayin CRM leads grid allows full DB exfiltration.

common questions

Is CVE-2026-41453 being exploited?

Not confirmed. CVE-2026-41453 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-41453?

CVE-2026-41453 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-41453?

Yes. A fix has been recorded for CVE-2026-41453. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-41453 affect?

CVE-2026-41453 affects Krayin CRM < 2.2.4, Leads DataGrid (LeadDataGrid.php), Self-hosted Krayin installations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-41453?

Upgrade to Krayin CRM 2.2.4, restrict leads access, rotate credentials, audit logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Krayin CRM < 2.2.4Leads DataGrid (LeadDataGrid.php)Self-hosted Krayin installations
impact

Authenticated users with leads access can inject via rotten_lead[in] HAVING clause to extract database contents, including credential hashes and config.

action required

Immediate action required

affected versions
krayin laravel-crm
  • affected< 2.2.4
vendor says fixed in2.2.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free