{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1522 exists.","fix":"No fix has been published for CVE-2024-1522 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1522 is a high-severity vulnerability in parisneo/lollms-webui, published on 30 Mar 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-1522 and fix it if it is affected.\n\nWhat it is: CVE-2024-1522 is a high-severity vulnerability in parisneo/lollms-webui, published on 30 Mar 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1522 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-1522/ (Markdown: https://insights.sbomify.com/CVE-2024-1522/index.md)","id":"CVE-2024-1522","markdown":"https://insights.sbomify.com/CVE-2024-1522/index.md","name":"CVE-2024-1522","record":{"aliases":["GHSA-4qp4-9mwx-276r"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"lollms-webui","requires_auth":"none","summary":"Attackers can execute arbitrary code on victim systems via CSRF in lollms-webui by tricking users into visiting a malicious webpage.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lollms_web_ui","vendor":"lollms"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A Cross-Site Request Forgery (CSRF) vulnerability in the parisneo/lollms-webui project allows remote attackers to execute arbitrary code on a victim's system. The vulnerability stems from the `/execute_code` API endpoint, which does not properly validate requests, enabling an attacker to craft a malicious webpage that, when visited by a victim, submits a form to the victim's local lollms-webui instance to execute arbitrary OS commands. This issue allows attackers to take full control of the victim's system without requiring direct network access to the vulnerable application.","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":"Cross-Site Request Forgery (CSRF) Leading to Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-1522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"EC-WEB FS-EZViewer(Web) - SQL Injection","id":"CVE-2024-1523"},"packages":[],"prev":{"headline":"Cross-site scripting in Elementor Website Builder Pro","id":"CVE-2024-1521"},"products":["parisneo/lollms-webui"],"published":"2024-03-30","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":"2024-08-01","vendors":["parisneo"]},"summary":"Attackers can execute arbitrary code on victim systems via CSRF in lollms-webui by tricking users into visiting a malicious webpage.","url":"https://insights.sbomify.com/CVE-2024-1522/"}