CVE-2024-0439 is a high severity (CVSS 8.8) improper privilege management flaw in AnythingLLM from Mintplex Labs. A user with the manager role could change settings that the interface hides from them by sending a standard HTTP request. Update to a release that includes the fix.
What's affected
The record names AnythingLLM by Mintplex Labs and gives no version range. The description is the maintainers' own: a manager should not be able to change a series of settings, the interface hides them, but a manager could still change them with their token through a standard HTTP request.
The linked commit is titled "prevent manager in multi-user from updating ENV via HTTP" and refers to pull request 576. We read the commit page but not the code in detail. The project's release notes will tell you which release first contains it, and we could not confirm a version number.
The weakness is CWE-269, improper privilege management. The setting is multi user mode, where roles such as manager and admin exist.
Severity: the record scores it 8.8 with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. The description says it is not a critical vulnerability, but that it needs patching to enforce the expected permission level. High on the CVSS scale and not critical in the maintainers' words are both consistent. It is not on the CISA Known Exploited Vulnerabilities list.
How to check if you're exposed
You are in scope if you run AnythingLLM in multi user mode and give anyone the manager role. In single user mode there are no roles to separate. Open the application's settings or about screen, note the version, and compare it with the release that includes the commit linked above. The project release notes are the source for that.
Also list who holds the manager role. The exposure is limited to those people, plus anyone who gets hold of a manager token.
What to do now
- Find every AnythingLLM instance you run and note whether it uses multi user mode.
- Update to a release that includes the fix. If the commit is not in your build, the fix is missing.
- Review the manager accounts, and demote or remove any that do not need it.
- Review the instance settings for changes you did not make, such as model provider keys and storage options.
- Rotate any keys held in those settings if you find unexplained changes.
Why it matters
Hiding a control in the interface is not access control. The server must check the role for every request, because anyone with a token can send requests without using the interface. This flaw is a plain case of that gap.
The impact in the vector is high on all three sides, because the settings in question configure the whole instance. For teams that run an internal AI workspace with shared roles, this is the case for treating role checks as a server side responsibility and testing them with direct requests.
Quick check
Is CVE-2024-0439 critical?
The maintainers say it is not a critical vulnerability. The CVSS score in the record is 8.8, which is high.
Does this affect single user installs?
The description concerns the manager role in multi user mode, so roles are the precondition. Check the release notes for details.
Sources
- Gold entry for CVE-2024-0439
- Fix commit 7200a06 in anything-llm
- huntr report (linked by the record; page content did not load)
Last reviewed: 19 October 2026.
