Filesystem writes via inadequate path sanitization
Published Jul 20, 2024 · Updated Oct 15, 2025
Path traversal in LoLLMS before 9.5.1 allows local users to write files outside the intended discussion database directory. The apply_settings function accepts discussion_db_name after sanitize_path fails to confine the resulting pathname to its intended parent directory. Exploitation requires local access to the settings application and can overwrite host files or interrupt the service.
Summary
What happened
Path traversal in LoLLMS before 9.5.1 allows local users to write files outside the intended discussion database directory. The apply_settings function accepts discussion_db_name after sanitize_path fails to confine the resulting pathname to its intended parent directory. Exploitation requires local access to the settings application and can overwrite host files or interrupt the service.
The record
- CVE
- CVE-2024-6281
- Published
- Jul 20, 2024
- Updated
- Oct 15, 2025
- Vendor
- ParisNeo
- Product
- LoLLMS
- Classifications
- CWE-22
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2024CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <9.5.1
- Affected versionversion=unspecified <9.5.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo