Security Digest · Vulnerability record

CVE-2024-4315: parisneo/lollms Local File Inclusion (LFI) attack

parisneo/lollms version 9.5 is vulnerable to Local File Inclusion (LFI) attacks due to insufficient path sanitization.

CVSS 9.1 Critical EPSS 1.0% · p63

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 1.0%, percentile 63: FIRST’s model estimates a 1.0% chance of exploitation activity in the next 30 days, higher than 63% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes lollms (PyPI) < 9.5.0, fixed in 9.5.0. Check your lockfile, including transitive dependencies.

What it is

parisneo/lollms version 9.5 is vulnerable to Local File Inclusion (LFI) attacks due to insufficient path sanitization. The sanitizepathfromendpoint function fails to properly sanitize Windows-style paths (backward slash \), allowing attackers to perform directory traversal attacks on Windows systems. This vulnerability can be exploited through various routes, including personalities and /delpreset, to read or delete any file on the Windows filesystem, compromising the system's availability.

From the GitHub advisory

parisneo/lollms version 9.5 is vulnerable to Local File Inclusion (LFI) attacks due to insufficient path sanitization. The sanitizepathfromendpoint function fails to properly sanitize Windows-style paths (backward slash \), allowing attackers to perform directory traversal attacks on Windows systems. This vulnerability can be exploited through various routes, including personalities and /delpreset, to read or delete any file on the Windows filesystem, compromising the system's availability.

Weakness type: CWE-22.

Product: lollms (PyPI) · Assigned by: @huntr_ai · Published: 2024-06-12

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIlollms< 9.5.09.5.0
VendorProductAffected versions (per CVE record)
parisneoparisneo/lollmsunspecified < 9.8

Severity scores

Scored byCVSSScoreVector
@huntr_ai3.09.1 CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
GitHub3.19.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 1.02% probability of exploitation activity in the next 30 days; percentile 63.

Timeline

  • — CVE record published by @huntr_ai
  • — GitHub-reviewed advisory GHSA-vqwr-q6cc-c242 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-vqwr-q6cc-c242 github.com
  2. CVE.org record CVE-2024-4315 cve.org
  3. NVD entry CVE-2024-4315 nvd.nist.gov

Other references from the CVE record and advisory

  1. huntr.com huntr.com
  2. github.com github.com

Critical PyPI advisories · Today’s Security Digest