VulnerabilityPublished 20 Mar 2025Updated 15 Oct 2025

CVE-2024-8251: mintplex-labs/anything-llm · SQL Injection

Affects mintplex-labs/anything-llmSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.2.2 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.2.2

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mintplex-labs/anything-llm to 1.2.2.

Affected software

Product	Affected	Fixed in
GitHubmintplex-labs/anything-llm`pkg:github/mintplex-labs/anything-llm`Other threats	Affected <1.2.2	Fixed in 1.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to mintplex-labs/anything-llm version 1.2.2 or later as soon as an official patch is released that addresses this Prisma injection vulnerability.
If you cannot patch yet, implement strict input validation and sanitization on all JSON inputs accepted by the "/embed/:embedId/stream-chat" API endpoint to reject or neutralize special query operators such as 'not', 'or', 'and', and others that can manipulate Prisma queries.
Employ parameterized queries or ORM features that safely handle user inputs without directly injecting them into query clauses.
Introduce application-layer access controls to restrict API usage to authenticated and authorized users, reducing the attack surface.
Monitor API logs for unusual query patterns or large data retrievals that may indicate exploitation attempts.
Conduct code reviews and security testing focusing on injection flaws in all endpoints that accept user-controlled JSON for database queries.
Educate developers on secure ORM usage and the risks of improper query construction.
Consider implementing Web Application Firewalls (WAF) with custom rules to detect and block suspicious JSON payloads targeting the vulnerable endpoint.
Regularly audit and update dependencies to incorporate security fixes promptly.

Description

A vulnerability in mintplex-labs/anything-llm prior to version 1.2.2 allows for Prisma injection. The issue exists in the API endpoint "/embed/:embedId/stream-chat" where user-provided JSON is directly taken to the Prisma library's where clause. An attacker can exploit this by providing a specially crafted JSON object, such as {"sessionId":{"not":"a"}}, causing Prisma to return all data from the table. This can lead to unauthorized access to all user queries in embedded chat mode.

Impact

For European organizations using mintplex-labs/anything-llm, especially those embedding chat functionalities that handle sensitive user queries or data, this vulnerability poses a risk of unauthorized data exposure. Attackers exploiting this flaw can retrieve all user queries processed by the embedded chat, potentially leaking confidential business information, personally identifiable information (PII), or intellectual property. This could lead to reputational damage, regulatory non-compliance (e.g., GDPR violations), and loss of customer trust. Since the vulnerability does not affect data integrity or availability, the primary concern is confidentiality. However, the ease of remote exploitation without authentication increases the threat level. Organizations in sectors such as finance, healthcare, legal, and technology that rely on embedded AI chat solutions are particularly at risk. Additionally, the lack of known exploits in the wild suggests that proactive mitigation can effectively prevent compromise. Failure to address this vulnerability could also invite targeted attacks from threat actors interested in data harvesting or espionage, especially given the growing use of AI-driven chat applications in Europe.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:20 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats