{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9920 exists.","fix":"No fix has been published for CVE-2024-9920 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9920 is a medium-severity vulnerability in parisneo/lollms-webui, published on 20 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-9920 and fix it if it is affected.\n\nWhat it is: CVE-2024-9920 is a medium-severity vulnerability in parisneo/lollms-webui, published on 20 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9920 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-9920/ (Markdown: https://insights.sbomify.com/CVE-2024-9920/index.md)","id":"CVE-2024-9920","markdown":"https://insights.sbomify.com/CVE-2024-9920/index.md","name":"CVE-2024-9920","record":{"aliases":["GHSA-54c7-72v9-gm27"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lollms Web UI","requires_auth":"low_privilege","summary":"Attackers can upload malicious files and execute them via the open_file API, leading to remote code execution in Lollms Web UI.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lollms_web_ui","vendor":"lollms"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"In version v12 of parisneo/lollms-webui, the 'Send file to AL' function allows uploading files with various extensions, including potentially dangerous ones like .py, .sh, .bat, and more. Attackers can exploit this by uploading files with malicious content and then using the '/open_file' API endpoint to execute these files. The vulnerability arises from the use of 'subprocess.Popen' to open files without proper validation, leading to potential remote code execution.","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":"Unrestricted File Upload and Execution in parisneo/lollms-webui","id":"CVE-2024-9920","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"TEAMPLUS TECHNOLOGY Team+ - SQL Injection","id":"CVE-2024-9921"},"packages":[],"prev":{"headline":"Missing Authentication Check in parisneo/lollms-webui","id":"CVE-2024-9919"},"products":["parisneo/lollms-webui"],"published":"2025-03-20","related":[{"cvss_score":9.8,"headline":"Improper Neutralization of Special Elements used in an OS Command in parisneo/lollms-webui","id":"CVE-2024-2359","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.8,"headline":"Path Traversal leading to Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-2360","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.8,"headline":"Remote Code Execution due to LFI in '/install_extension' in parisneo/lollms-webui","id":"CVE-2024-4320","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.8,"headline":"Path Traversal leading to Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-2358","kev_date_added":null,"published":"2024-05-16"},{"cvss_score":9.8,"headline":"Remote Code Execution via `/apply_settings` and `/execute_code` in parisneo/lollms-webui","id":"CVE-2024-4326","kev_date_added":null,"published":"2024-05-16"},{"cvss_score":9.8,"headline":"Path Traversal Vulnerability in parisneo/lollms-webui","id":"CVE-2024-1511","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.8,"headline":"OS Command Injection in parisneo/lollms-webui","id":"CVE-2024-1520","kev_date_added":null,"published":"2024-04-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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["parisneo"]},"summary":"Attackers can upload malicious files and execute them via the open_file API, leading to remote code execution in Lollms Web UI.","url":"https://insights.sbomify.com/CVE-2024-9920/"}