CVE-2024-5211
No exploitation reported by the sources we read.
- Published2024-06-12
- Fixed in1.0.0
- WeaknessCWE-29
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A path traversal vulnerability in mintplex-labs/anything-llm allowed a manager to bypass the `normalizePath()` function, intended to defend against path traversal attacks. This vulnerability enables the manager to read, delete, or overwrite the 'anythingllm.db' database file and other files stored in the 'storage' directory, such as internal communication keys and .env secrets. Exploitation of this vulnerability could lead to application compromise, denial of service (DoS) attacks, and unauthorized admin account takeover. The issue stems from improper validation of user-supplied input in the process of setting a custom logo for the app, which can be manipulated to achieve arbitrary file read, deletion, or overwrite, and to execute a DoS attack by deleting critical files required for the application's operation.
Timeline
dates in UTC- 2024-06-1212:15CVE publishedNVD
Versions per branch
NVD · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | < 1.0.0 | 1.0.0 | NVD · CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As @huntr_ai, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- mintplex-labs/anything-llmAffected
- < 1.0.0fixed in 1.0.0custom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-06-12
Fix
- Update Mintplexlabs anythingllm to 1.0.0
Advisories and patches
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionnone2024-06-12
- NVDCVSS 3.17.2read 2026-10-23
- CNACVSS 3.09.1known since 2026-10-23
- CNAweakness (CWE)CWE-29known since 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-11-18
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2024-46451same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-v9ph-8hf4-hgrxsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Published
- 2024-06-12
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-v9ph-8hf4-hgrx
Frequently asked questions
What is CVE-2024-5211?
Is CVE-2024-5211 actively exploited?
What is the CVSS score for CVE-2024-5211?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-v9ph-8hf4-hgrx
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- CISA Vulnrichment · CC0-1.0