CVE-2026-41453: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in krayin laravel-crm
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.
AI Analysis
Technical Summary
CVE-2026-41453 is a blind SQL injection vulnerability affecting Krayin laravel-crm before version 2.2.4. The vulnerability exists because the rotten_lead[in] query parameter is directly concatenated into a havingRaw() SQL call in LeadDataGrid.php without proper parameterization or sanitization. This improper neutralization of special elements in SQL commands enables authenticated users with leads access to inject arbitrary SQL code into the HAVING clause. Exploitation techniques include time-based and boolean-based blind injection, potentially allowing attackers to extract the entire database contents, including sensitive user credentials and CRM data.
Potential Impact
Successful exploitation of this vulnerability can lead to unauthorized disclosure of sensitive information stored in the database, including user credential hashes, CRM records, and application configuration data. This compromises the confidentiality and integrity of the affected system's data. The vulnerability requires authenticated access with leads permissions but does not require user interaction or elevated privileges beyond that. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects versions prior to 2.2.4, upgrading to version 2.2.4 or later is recommended once an official fix is available. Until then, restrict leads access to trusted users only and monitor for suspicious activity related to the rotten_lead[in] parameter. Avoid using vulnerable versions in production environments.
CVE-2026-41453: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in krayin laravel-crm
Description
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 v4.0
Score 8.7high
Affected software
krayin
laravel-crm
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41453 is a blind SQL injection vulnerability affecting Krayin laravel-crm before version 2.2.4. The vulnerability exists because the rotten_lead[in] query parameter is directly concatenated into a havingRaw() SQL call in LeadDataGrid.php without proper parameterization or sanitization. This improper neutralization of special elements in SQL commands enables authenticated users with leads access to inject arbitrary SQL code into the HAVING clause. Exploitation techniques include time-based and boolean-based blind injection, potentially allowing attackers to extract the entire database contents, including sensitive user credentials and CRM data.
Potential Impact
Successful exploitation of this vulnerability can lead to unauthorized disclosure of sensitive information stored in the database, including user credential hashes, CRM records, and application configuration data. This compromises the confidentiality and integrity of the affected system's data. The vulnerability requires authenticated access with leads permissions but does not require user interaction or elevated privileges beyond that. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects versions prior to 2.2.4, upgrading to version 2.2.4 or later is recommended once an official fix is available. Until then, restrict leads access to trusted users only and monitor for suspicious activity related to the rotten_lead[in] parameter. Avoid using vulnerable versions in production environments.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-04-20T16:07:47.309Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a70bf62bf32cb7a34daf16e
Added to database: 08/03/2026, 16:18:42 UTC
Last enriched: 08/15/2026, 13:45:03 UTC
Last updated: 09/17/2026, 22:01:35 UTC
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.