{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41453 exists.","fix":"No fix has been published for CVE-2026-41453 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41453 is a high-severity SQL injection vulnerability in krayin laravel-crm, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41453 and fix it if it is affected.\n\nWhat it is: CVE-2026-41453 is a high-severity SQL injection vulnerability in krayin laravel-crm, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41453 exists.\n\nAffected product: krayin laravel-crm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41453/ (Markdown: https://insights.sbomify.com/CVE-2026-41453/index.md)","id":"CVE-2026-41453","markdown":"https://insights.sbomify.com/CVE-2026-41453/index.md","name":"CVE-2026-41453","record":{"aliases":["GHSA-8879-fh4f-q3qm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Krayin CRM","requires_auth":"low_privilege","summary":"Authenticated users can exploit blind SQL injection in Krayin CRM to extract sensitive database contents, including credentials and records.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Krayin CRM \u003c 2.2.4 Blind SQL Injection via LeadDataGrid.php rotten_lead Parameter","id":"CVE-2026-41453","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"WeKan \u003c 8.35 Missing Authorization via Integration REST API","id":"CVE-2026-41454"},"packages":[],"prev":{"headline":"Krayin CRM 2.2.4 Missing Authentication via install/api/admin-config-setup","id":"CVE-2026-41452"},"products":["laravel-crm"],"published":"2026-08-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["krayin"]},"summary":"Authenticated users can exploit blind SQL injection in Krayin CRM to extract sensitive database contents, including credentials and records.","url":"https://insights.sbomify.com/CVE-2026-41453/"}