VulnerabilityPublished 20 Jun 2024Updated 15 Oct 2025

CVE-2024-5213: mintplex-labs/anything-llm · Insertion of Sensitive Information Into Sent Data

Affects mintplex-labs/anything-llmSource CVE Database V5

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

Data as of 26 Oct 2026, 14:05 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 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.5.4

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 Jun 2024
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.5.4.

Affected software

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

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

AI-suggested

In the interim, developers should modify the backend API to exclude sensitive fields such as password hashes from all responses sent to the frontend. Implement strict response filtering and data sanitization to ensure only necessary user information is exposed. Conduct a thorough code review and audit all API endpoints for similar sensitive data exposures. Enforce strong password policies and consider multi-factor authentication to reduce the risk from compromised credentials. Monitor logs for unusual login activity or failed authentication attempts that could indicate brute-force attacks. Educate developers on secure coding practices regarding sensitive data handling. Additionally, rotate user credentials if hashes are suspected to have been exposed. Network segmentation and least privilege access controls can limit the impact of compromised accounts. Finally, maintain up-to-date backups and incident response plans to quickly respond to any breach.

Description

In mintplex-labs/anything-llm versions up to and including 1.5.3, an issue was discovered where the password hash of a user is returned in the response after login (`POST /api/request-token`) and after account creations (`POST /api/admin/users/new`). This exposure occurs because the entire User object, including the bcrypt password hash, is included in the response sent to the frontend. This practice could potentially lead to sensitive information exposure despite the use of bcrypt, a strong hashing algorithm. It is recommended not to expose any clues about passwords to the frontend.

Impact

For European organizations using mintplex-labs/anything-llm, this vulnerability poses a significant confidentiality risk. Exposure of password hashes can lead to offline brute-force attacks, potentially compromising user credentials and enabling unauthorized access to systems and data. This is particularly critical for organizations handling sensitive personal data, intellectual property, or operating in regulated sectors such as finance, healthcare, and government. The breach of password hashes could also facilitate lateral movement within networks if credentials are reused or weak. Although the vulnerability does not affect integrity or availability directly, the compromise of user accounts can lead to further attacks, data exfiltration, and reputational damage. The medium severity rating reflects the balance between the difficulty of exploitation (high complexity) and the high confidentiality impact. European entities relying on this software for AI or machine learning workloads may face operational disruptions if attackers leverage compromised credentials to escalate privileges or disrupt services.

CWE-201Insertion of Sensitive Information Into Sent Data (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Requirements
Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
Implementation
Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere.
System Configuration
Setup default error messages so that unexpected errors do not disclose sensitive information.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Exploiting Incorrectly Configured SSL/TLS (opens in a new tab)
WiFi MAC Address Tracking (opens in a new tab)
WiFi SSID Tracking (opens in a new tab)
Cellular Broadcast Message Request (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:30 UTC

WeaknessesCWE-201

Technical details

References

Community reviews

Related threats