# CVE-2024-3110: Stored XSS leading to admin account takeover in mintplex-labs/anything-llm > Stored XSS allows managers to steal admin tokens via malicious URLs, leading to admin account takeover and privilege escalation. - **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 6 Jun 2024 - **Updated:** 1 Aug 2024 - **Also known as:** GHSA-87vx-c24v-wf2q ## What is CVE-2024-3110? CVE-2024-3110 is a high-severity cross-site scripting vulnerability in Mintplexlabs Anythingllm, published on 6 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description A stored Cross-Site Scripting (XSS) vulnerability exists in the mintplex-labs/anything-llm application, affecting versions up to and including the latest before 1.0.0. The vulnerability arises from the application's failure to properly sanitize and validate user-supplied URLs before embedding them into the application UI as external links with custom icons. Specifically, the application does not prevent the inclusion of 'javascript:' protocol payloads in URLs, which can be exploited by a user with manager role to execute arbitrary JavaScript code in the context of another user's session. This flaw can be leveraged to steal the admin's authorization token by crafting malicious URLs that, when clicked by the admin, send the token to an attacker-controlled server. The attacker can then use this token to perform unauthorized actions, escalate privileges to admin, or directly take over the admin account. The vulnerability is triggered when the malicious link is opened in a new tab using either the CTRL + left mouse button click or the mouse scroll wheel click, or in some non-updated versions of modern browsers, by directly clicking on the link. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-3110? It affects 1 product. Products: Mintplexlabs Anythingllm. ## How do I fix CVE-2024-3110? No fix has been published for CVE-2024-3110 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-3110 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3110 exists. ## Other vulnerabilities in Mintplexlabs Anythingllm - [CVE-2024-3025](https://insights.sbomify.com/CVE-2024-3025/): Path Traversal in mintplex-labs/anything-llm (critical 9.9) - [CVE-2024-0455](https://insights.sbomify.com/CVE-2024-0455/): SSRF on AWS deployed instances of AnythingLLM via /metadata (critical 9.9) - [CVE-2026-32626](https://insights.sbomify.com/CVE-2026-32626/): AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection (critical 9.7) - [CVE-2024-3104](https://insights.sbomify.com/CVE-2024-3104/): Remote Code Execution in mintplex-labs/anything-llm (critical 9.6) - [CVE-2024-3149](https://insights.sbomify.com/CVE-2024-3149/): SSRF in mintplex-labs/anything-llm (critical 9.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3110 and fix it if it is affected. What it is: CVE-2024-3110 is a high-severity cross-site scripting vulnerability in Mintplexlabs Anythingllm, published on 6 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3110 exists. Affected product: Mintplexlabs Anythingllm. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-3110/ (Markdown: https://insights.sbomify.com/CVE-2024-3110/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3110 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3110 - OSV: https://osv.dev/vulnerability/CVE-2024-3110 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3110/ Summaries are generated and may contain mistakes; the official description above is the record.