CVE-2024-2624 is a path traversal and arbitrary file upload in the parisneo lollms-webui application, in the switch_personal_path endpoint, scored Critical at 9.8 and fixed in version 9.4. Severity is Critical at 9.8. Upgrade to version 9.4 or later. The sections below cover affected versions, checks and next steps.
What's affected
- The record says the issue affects the latest version at the time and is fixed in version 9.4.
- The affected endpoint is switch_personal_path in the lollms_user.py file of the lollms core server code.
- Treat any release before 9.4 as vulnerable unless the project's release notes say otherwise.
The NVD record gives a CVSS score of 9.8 with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Published 2024-06-06.
How to check if you're exposed
- If you installed from git, run
git describe --tagsinside the lollms-webui folder to see the release. - Check the application's version display in its settings or about page.
- Check whether the web UI is reachable from beyond localhost, for example with
ss -ltnpon the host. - Search the project's repository for the fix commit named in Sources.
What to do now
- Upgrade lollms-webui to 9.4 or later.
- Do not expose the web UI to the internet. Bind it to localhost or place it behind authentication.
- Back up and then review the personal data and configs folders for unexpected files or edits.
- Review your configuration files for changes you did not make.
If this software reaches you as part of something you build, the free in-browser dependency scan at gold.safeguard.sh/scan lists known vulnerabilities in your manifests, and reachability analysis helps you see which ones your code can actually trigger.
Why it matters
The record says the path parameter was not sanitised, so a caller could point the application at arbitrary file system paths. That enables arbitrary file uploads, exposure of personal data, and the overwriting of configuration files, which could lead to remote code execution.
Path traversal and its variants are classic input handling bugs. The fix is to resolve paths and confirm they stay inside an allowed directory. The tagged weaknesses are CWE-29 and CWE-22. Local AI tools are often run casually and exposed on networks, which is why a flaw like this deserves quick attention.
The record tags the weakness as CWE-22. See the Gold pages for more on the class.
The record's Known Exploited Vulnerabilities flag is false, so CISA has not listed it as exploited.
Tools that run local models often hold keys, prompts and personal data in their configuration, so the data at risk can be more than the app itself.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which version fixes it?
The NVD description says it is fixed in version 9.4. Confirm against the project's release notes.
Is it safe if the UI is only on my laptop?
Binding to localhost greatly reduces exposure, but other local software and browser based tricks can still reach it, so upgrade anyway.
Sources
Last reviewed: 19 October 2026.
