CVE-2024-4267 is a Critical (CVSS 9.8) command injection in parisneo lollms-webui version 9.5. The open_file function passes a user supplied path to subprocess.Popen without enough checking, so a crafted path can run system commands or read files. The record names no fixed version, so use the newest release.
What's affected
- Product: lollms-webui from parisneo, version 9.5, in the open_file module.
- Fixed version: not stated in the record. The only reference is a huntr report I did not fetch. Check the project's releases.
- Severity: Critical, CVSS 9.8, network based with no privileges and no user interaction.
- Cause in the record: subprocess.Popen is used unsafely to open files based on paths the user supplies.
- Exploitation: KEV is false. No page I read reports attacks.
How to check if you're exposed
If you run lollms-webui, find its version in the application or the repository you installed from. Version 9.5 is the one named in the record.
If you installed from a git checkout, git describe or git log -1 shows where you are. Then check how the service is reachable: is it bound only to localhost, or open on a LAN or the internet? Local only use sharply reduces exposure.
What to do now
- Find every lollms-webui instance, including personal machines and test servers.
- Update to the newest upstream release and read its notes for mention of open_file.
- Bind the service to 127.0.0.1, or put it behind authentication and a firewall.
- Run it under an account that cannot reach secrets, SSH keys or cloud credentials.
- Review the host for unexpected processes or files if the UI was ever internet facing.
Why it matters
The record maps this to CWE-77, command injection. The code builds a command around a file path from the client. When the path is not validated, characters in it can alter the command that runs.
Tools that run local AI models often start as personal projects and end up on shared servers. They tend to run with the user's full rights and have no login screen, which is why a flaw like this is more dangerous than the install base suggests.
Quick check
Is lollms-webui safe on localhost only?
It lowers the exposure a lot, because outsiders cannot reach it. Other software on the machine, or a browser based attack, may still reach a local port, so update anyway.
Which version fixes it?
The record names none. Use the latest release.
Scan your own dependencies
Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan checks a manifest against known advisories, and the Gold directory keeps this record's details in one place.
Sources
The NVD record for CVE-2024-4267 (published 2024-05-22) supplied the description, score and weakness data. Pages marked fetched were read for this post. The others are listed in the record and were not read.
Last reviewed: 19 October 2026.
