CVE-2024-13059

AnythingLLM prior to version 1.3.1 contains a path traversal vulnerability (CWE-22/CWE-29) caused by improper handling of non-ASCII filenames passed through the multer library, where the filename transformation can introduce '../' sequences that are never sanitized. An authenticated attacker holding a manager or admin role can submit a crafted filename to trigger a file write outside the intended upload directory. By writing files to arbitrary server locations, the attacker can escalate to remote code execution on the host running AnythingLLM. All self-hosted AnythingLLM deployments running a version before 1.3.1 are affected, and exploitation requires privileged (manager/admin) application access rather than anonymous access. There is no confirmed in-the-wild exploitation and the issue is not in CISA KEV, but a public proof-of-concept exists via the huntr bounty report and the EPSS score of 21.3% (97th percentile) indicates an elevated likelihood of exploitation within the next 30 days.

What to do: Upgrade AnythingLLM to version 1.3.1 or later to obtain the sanitized filename handling. Until upgraded, audit manager and admin accounts for unexpected privileges, review upload activity for filenames containing non-ASCII characters or '../' sequences, and check the host for files written outside the expected upload directories. Internet-facing deployments should be patched with priority given the public PoC and rising EPSS probability.