Advisory record · GHSA-6h64-g7cj-hj56

A path traversal vulnerability exists in the api open_personality_folder endpoint of parisneo/lollms-webui. This vulnerability allows an attacker to read any folder in the personality_folder on the...

CVSS 4.4 MediumEPSS 0.0035 · 29th percentile

Published by the GitHub Advisory Database at 11 Oct 2024, 16:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
lollmsPyPI<28ee567a9a120967215ff19b96ab7515ce469620 || <5.9.028ee567a9a120967215ff19b96ab7515ce469620, 5.9.0
Identifiers
GHSA-6h64-g7cj-hj56 · CVE-2024-6985 · PYSEC-2024-122
Weakness (CWE)
CWE-23
Published
11 Oct 2024
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The lollms package (PyPI) versions before 5.9.0 are vulnerable to path traversal in the open_personality_folder API endpoint of lollms-webui. An attacker can use this to read folders outside the intended personality folder on the host, even when sanitize_path is set, because the personality_folder parameter is not properly sanitized. The source does not state what network or account access is required. Upgrade lollms to version 5.9.0 or later.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.4 Medium 3.0 CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0035, the 29th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 11 Oct 2024. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.