{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-5213 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-5213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5213 is a medium-severity vulnerability in Mintplexlabs Anythingllm, published on 20 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-5213 and fix it if it is affected.\n\nWhat it is: CVE-2024-5213 is a medium-severity vulnerability in Mintplexlabs Anythingllm, published on 20 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-5213 in the wild and no public exploit code.\n\nAffected product: Mintplexlabs Anythingllm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-5213/ (Markdown: https://insights.sbomify.com/CVE-2024-5213/index.md)","id":"CVE-2024-5213","markdown":"https://insights.sbomify.com/CVE-2024-5213/index.md","name":"CVE-2024-5213","record":{"aliases":["GHSA-c72r-fww5-rpch"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AnythingLLM web app","requires_auth":"low_privilege","summary":"Attackers can obtain bcrypt password hashes from API responses, potentially aiding offline cracking attacks against user accounts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"anythingllm","vendor":"mintplexlabs"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Exposure of Sensitive Information in mintplex-labs/anything-llm","id":"CVE-2024-5213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mintplexlabs:anythingllm","products":["mintplexlabs:anythingllm"],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-5214"},"packages":[],"prev":{"headline":"tagDiv Composer \u003c= 5.0 - Reflected Cross-Site Scripting via envato_code[]","id":"CVE-2024-5212"},"products":["mintplex-labs/anything-llm"],"published":"2024-06-20","related":[{"cvss_score":9.9,"headline":"Path Traversal in mintplex-labs/anything-llm","id":"CVE-2024-3025","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.9,"headline":"SSRF on AWS deployed instances of AnythingLLM via /metadata","id":"CVE-2024-0455","kev_date_added":null,"published":"2024-02-25"},{"cvss_score":9.7,"headline":"AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection","id":"CVE-2026-32626","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":9.6,"headline":"Remote Code Execution in mintplex-labs/anything-llm","id":"CVE-2024-3104","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.6,"headline":"SSRF in mintplex-labs/anything-llm","id":"CVE-2024-3149","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.6,"headline":"Default user role exporting save state of instance","id":"CVE-2024-0765","kev_date_added":null,"published":"2024-03-03"},{"cvss_score":9.6,"headline":"Privileged User using traversal to read system files","id":"CVE-2024-0550","kev_date_added":null,"published":"2024-02-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["mintplex-labs"]},"summary":"Attackers can obtain bcrypt password hashes from API responses, potentially aiding offline cracking attacks against user accounts.","url":"https://insights.sbomify.com/CVE-2024-5213/"}