{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1601 exists.","fix":"No fix has been published for CVE-2024-1601 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1601 is a high-severity SQL injection vulnerability in parisneo/lollms-webui, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-1601 and fix it if it is affected.\n\nWhat it is: CVE-2024-1601 is a high-severity SQL injection vulnerability in parisneo/lollms-webui, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1601 exists.\n\nAffected product: parisneo/lollms-webui. 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-1601/ (Markdown: https://insights.sbomify.com/CVE-2024-1601/index.md)","id":"CVE-2024-1601","markdown":"https://insights.sbomify.com/CVE-2024-1601/index.md","name":"CVE-2024-1601","record":{"aliases":["GHSA-v84m-cf86-322v"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"lollms-webui","requires_auth":"none","summary":"An attacker can delete all discussion and message data via SQL injection in the delete_discussion endpoint of lollms-webui.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lollms-webui","vendor":"lollms"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"An SQL injection vulnerability exists in the `delete_discussion()` function of the parisneo/lollms-webui application, allowing an attacker to delete all discussions and message data. The vulnerability is exploitable via a crafted HTTP POST request to the `/delete_discussion` endpoint, which internally calls the vulnerable `delete_discussion()` function. By sending a specially crafted payload in the 'id' parameter, an attacker can manipulate SQL queries to delete all records from the 'discussion' and 'message' tables. This issue is due to improper neutralization of special elements used in an SQL command.","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":"SQL Injection in parisneo/lollms-webui","id":"CVE-2024-1601","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Stored XSS leading to RCE in parisneo/lollms-webui","id":"CVE-2024-1602"},"packages":[],"prev":{"headline":"Local File Inclusion in parisneo/lollms-webui","id":"CVE-2024-1600"},"products":["parisneo/lollms-webui"],"published":"2024-04-16","related":[{"cvss_score":8.4,"headline":"Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-4267","kev_date_added":null,"published":"2024-05-22"},{"cvss_score":8.2,"headline":"Authentication Bypass in parisneo/lollms-webui","id":"CVE-2024-1646","kev_date_added":null,"published":"2024-04-16"},{"cvss_score":7.3,"headline":"XSS and Open Redirect via SVG File Upload in parisneo/lollms-webui","id":"CVE-2024-5125","kev_date_added":null,"published":"2024-11-14"},{"cvss_score":5.3,"headline":"Uncontrolled Resource Consumption in parisneo/lollms-webui","id":"CVE-2024-1569","kev_date_added":null,"published":"2024-04-16"},{"cvss_score":4.4,"headline":"CSRF in Servers Configurations in parisneo/lollms-webui","id":"CVE-2024-4839","kev_date_added":null,"published":"2024-06-24"},{"cvss_score":4.4,"headline":"CSRF in restart_program in parisneo/lollms-webui","id":"CVE-2024-4403","kev_date_added":null,"published":"2024-06-10"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["parisneo"]},"summary":"An attacker can delete all discussion and message data via SQL injection in the delete_discussion endpoint of lollms-webui.","url":"https://insights.sbomify.com/CVE-2024-1601/"}