{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-46366 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-46366 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-46366 is a high-severity cross-site scripting vulnerability in n/a, published on 27 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-46366 and fix it if it is affected.\n\nWhat it is: CVE-2024-46366 is a high-severity cross-site scripting vulnerability in n/a, published on 27 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-46366 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2024-46366/ (Markdown: https://insights.sbomify.com/CVE-2024-46366/index.md)","id":"CVE-2024-46366","markdown":"https://insights.sbomify.com/CVE-2024-46366/index.md","name":"CVE-2024-46366","record":{"aliases":["GHSA-wqc2-gwgp-9p7w"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Krayin CRM","requires_auth":"none","summary":"Remote attackers can execute arbitrary client-side template code via lead creation, leading to privilege escalation in Krayin CRM.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"krayin_crm","vendor":"webkul"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"A Client-side Template Injection (CSTI) vulnerability in Webkul Krayin CRM 1.3.0 allows remote attackers to execute arbitrary client-side template code by injecting a malicious payload during the lead creation process. This can lead to privilege escalation when the payload is executed, granting the attacker elevated permissions within the CRM system.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2024-46366","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-46367"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2024-46362"},"products":["n/a"],"published":"2024-09-27","related":[{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2024-46367","kev_date_added":null,"published":"2024-09-27"},{"cvss_score":8.8,"headline":"Webkul Krayin CRM has Broken Object-Level Authorization (BOLA) in the /Settings/UserController.php","id":"CVE-2026-38529","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":8.1,"headline":"Webkul Krayin CRM has Broken Object-Level Authorization (BOLA) in the /Controllers/Lead/LeadController.php","id":"CVE-2026-38530","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":8.1,"headline":"Webkul Krayin CRM has Broken Object-Level Authorization (BOLA) in the /Contact/Persons/PersonController.php","id":"CVE-2026-38532","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":7.1,"headline":"Krayin CRM vulnerable to Cross Site Scripting (XSS) via the organization name","id":"CVE-2024-45932","kev_date_added":null,"published":"2024-10-07"},{"cvss_score":5.1,"headline":"Webkul Krayin CRM SVG File edit cross site scripting","id":"CVE-2025-3568","kev_date_added":null,"published":"2025-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-27","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary client-side template code via lead creation, leading to privilege escalation in Krayin CRM.","url":"https://insights.sbomify.com/CVE-2024-46366/"}