CVE-2024-4881 is a high severity path traversal in parisneo/lollms, scored 7.5. On Windows, backslashes in a file path escape the intended folder, so unauthenticated users can read arbitrary files. The record's version data conflicts, so verify the fix commit.
What's affected
The description says the flaw affects version 9.4.0 and potentially earlier, but is "fixed in version 5.9.0". Those two statements cannot both be read at face value, since 5.9.0 is lower than 9.4.0. NVD's own product match is a wildcard range. I could not retrieve the referenced fix commit page, so I cannot settle which release first contains the fix.
What is clear: the description ties the problem to the /user_infos endpoint and to Windows, where paths use backslashes. Linux deployments are described as protected by different path handling, though that is the record's framing, not a guarantee.
The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N: network, no privileges, no interaction, high confidentiality impact. The weaknesses are CWE-22, path traversal, and CWE-36, absolute path traversal.
How to check if you're exposed
Find where LoLLMs runs, particularly on Windows machines or Windows containers. If you installed it with pip:
pip show lollms
If you run from a git checkout, compare your commit with the fix commit referenced in the record (95ad36e in the parisneo/lollms repository):
git branch --contains 95ad36eeffc6a6be3e3f35ed35a384d768f0ecf6
An empty result means your checkout does not include that commit. Also check whether the web service is bound to anything other than localhost.
What to do now
- List LoLLMs installs and mark the Windows ones first.
- Update to a build that includes the fix commit, and confirm using the git check above or the project's release notes.
- Bind the service to localhost or place it behind authentication and a firewall.
- Move secrets and environment files out of any directory the app account can read broadly, and run the service under a low privilege account.
- Rotate any API keys stored on a host that was exposed to untrusted networks.
Why it matters
Path traversal appears when code builds a file path from user input and does not make sure the result stays inside an intended folder. Checks written for forward slashes can miss backslashes, which Windows accepts as separators. That is the cross-platform gap the description names.
The consequence listed in the record is exposure of environment variables, database files and configuration files. For a tool that connects to language model services, those files often include API keys, so a read-only bug can become a spend and data problem.
The record does not mark this CVE as exploited in the wild and it is not in the CISA KEV catalog.
Quick check
Why does the version information look inconsistent?
The description names 9.4.0 as affected and 5.9.0 as the fixed version. Treat the commit as the source of truth and check the project.
Are Linux hosts affected?
The description frames the issue around Windows path handling. Still verify your build includes the fix commit.
Sources
- Fix commit in parisneo/lollms (page could not be retrieved)
- huntr report (page could not be retrieved)
Last reviewed: 19 October 2026.
