{"answers":{"affected":"3 open source packages ship an affected version, including lollms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4881 exists.","fix":"Upgrade lollms to a fixed version for your release line: 5.9.0 or 9.5.0.","what":"CVE-2024-4881 is a high-severity path traversal vulnerability in parisneo/lollms, published on 6 Jun 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-4881 and fix it if it is affected.\n\nWhat it is: CVE-2024-4881 is a high-severity path traversal vulnerability in parisneo/lollms, published on 6 Jun 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-4881 exists.\n\nAffected packages and fixed versions:\n- lollms (PyPI): affected all versions; fixed in 5.9.0\n- lollms (PyPI): affected all versions; fixed in 9.5.0\n- lollms (PyPI): affected all versions; fixed in 9.5.0\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-4881/ (Markdown: https://insights.sbomify.com/CVE-2024-4881/index.md)","id":"CVE-2024-4881","markdown":"https://insights.sbomify.com/CVE-2024-4881/index.md","name":"CVE-2024-4881","record":{"aliases":["GHSA-p8h7-c8gw-6x8c","PYSEC-2024-108"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"lollms application","requires_auth":"none","summary":"Attackers can exploit improper path validation to read or delete sensitive files on Windows systems via the /user_infos endpoint.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lollms","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:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-36","name":"Absolute Path Traversal"}],"description":"A path traversal vulnerability exists in the parisneo/lollms application, affecting version 9.4.0 and potentially earlier versions, but fixed in version 5.9.0. The vulnerability arises due to improper validation of file paths between Windows and Linux environments, allowing attackers to traverse beyond the intended directory and read any file on the Windows system. Specifically, the application fails to adequately sanitize file paths containing backslashes (`\\`), which can be exploited to access the root directory and read, or even delete, sensitive files. This issue was discovered in the context of the `/user_infos` endpoint, where a crafted request using backslashes to reference a file (e.g., `\\windows\\win.ini`) could result in unauthorized file access. The impact of this vulnerability includes the potential for attackers to access sensitive information such as environment variables, database files, and configuration files, which could lead to further compromise of the system.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Path Traversal in parisneo/lollms","id":"CVE-2024-4881","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"URL Redirection to Arbitrary Site Exists in Sitefinity","id":"CVE-2024-4882"},"packages":[{"ecosystem":"PyPI","fixed":["5.9.0"],"introduced":["0"],"last_affected":[],"package":"lollms","purl":"pkg:pypi/lollms","source":"PYSEC-2024-108"},{"ecosystem":"PyPI","fixed":["9.5.0"],"introduced":["0"],"last_affected":[],"package":"lollms","purl":null,"source":"GHSA-p8h7-c8gw-6x8c"},{"ecosystem":"PyPI","fixed":["9.5.0"],"introduced":["0"],"last_affected":[],"package":"lollms","purl":"pkg:pypi/lollms","source":"GHSA-p8h7-c8gw-6x8c"}],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-4880"},"products":["parisneo/lollms"],"published":"2024-06-06","related":[{"cvss_score":9.8,"headline":"Improper Access Control via Weak JWT Token in parisneo/lollms","id":"CVE-2026-1114","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Path Traversal in parisneo/lollms","id":"CVE-2024-3429","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.6,"headline":"Stored XSS in parisneo/lollms","id":"CVE-2026-1115","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":8.7,"headline":"Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms","id":"CVE-2026-12228","kev_date_added":null,"published":"2026-07-18"},{"cvss_score":8.3,"headline":"Insecure Direct Object Reference (IDOR) in parisneo/lollms","id":"CVE-2026-0562","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) in parisneo/lollms","id":"CVE-2026-1116","kev_date_added":null,"published":"2026-04-12"},{"cvss_score":7.6,"headline":"CSRF Vulnerability in parisneo/lollms XTTS Server","id":"CVE-2024-4499","kev_date_added":null,"published":"2024-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"Attackers can exploit improper path validation to read or delete sensitive files on Windows systems via the /user_infos endpoint.","url":"https://insights.sbomify.com/CVE-2024-4881/"}