path traversal vulnerability was identified in the parisneo/lollms-webui

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.0 · CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2024-4330: 0.29% estimated exploitation activity in the next 30 days; percentile 21.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A path traversal vulnerability was identified in the parisneo/lollms-webui repository, specifically within version 9.6. The vulnerability arises due to improper handling of user-supplied input in the 'listpersonalities' endpoint. By crafting a malicious HTTP request, an attacker can traverse the directory structure and view the contents of any folder, albeit limited to subfolder names only. This issue was demonstrated via a specific HTTP request that manipulated the 'category' parameter to access arbitrary directories. The vulnerability is present in the code located at the 'endpoints/lollmsadvanced.py' file.

Published by the source

2 Jun 2024, 22:30 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:13 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9p73-x86v-jw57

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9p73-x86v-jw57

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-4330

Advisory: path traversal vulnerability was identified in the parisneo/lollms-webui
IDs: CVE-2024-4330, GHSA-9p73-x86v-jw57
Record: https://patchnext.com/advisories/cve-2024-4330 (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI lollms: affected >= 9.6, <= 9.6

## Suggested inspection (read-only)
- `python -m pip show lollms`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lollms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9p73-x86v-jw57 (OSV record GHSA-9p73-x86v-jw57 lists affected ranges: PyPI lollms >=9.6 <=9.6)
- Verified: https://github.com/advisories/GHSA-9p73-x86v-jw57 (GitHub-reviewed advisory GHSA-9p73-x86v-jw57 lists affected ranges: PyPI lollms >=9.6 <=9.6)

Commands are suggestions: review each one before running it.