CVE-2024-5225: SQL Injection Vulnerability in LiteLLM
litellm
An SQL injection vulnerability exists in LiteLLM within the spend logs endpoint due to improper neutralization of the api_key parameter. Successful exploitation could lead to unauthorized data access and manipulation.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 6.4
- EPSS
- <0.01 · top 63% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 6 Jun 2024
- last update
- 6 Jun 2024
- CVE ids
Timeline · 1
- 6 Jun 2024CVE-2024-5225: SQL injection in litellm
Sources · 1
Advisories and databases
- 2024-06-06CVE-2024-5225: SQL injection in litellmGitHub Advisory Database · github.com/advisories/GHSA-h6m6-jj8v-94jj
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- tags
- sql-injection
- dates
- happened 6 Jun 2024 · first reported 6 Jun 2024
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2024-5225: SQL Injection Vulnerability in LiteLLM https://gcdradar.vercel.app/incidents/cve-2024-5225-sql-injection-vulnerability-in-litellm · AIR-2024-0128 · closed 2024-06-06 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2024-06-06 - AI role: Attack on AI - Products: litellm - CVE ids: CVE-2024-5225 - CVSS: 6.4 ## Summary An SQL injection vulnerability exists in LiteLLM within the spend logs endpoint due to improper neutralization of the api_key parameter. Successful exploitation could lead to unauthorized data access and manipulation. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2024-06-06: CVE-2024-5225: SQL injection in litellm (https://github.com/advisories/GHSA-h6m6-jj8v-94jj) ## Sources - 2024-06-06 GitHub Advisory Database: CVE-2024-5225: SQL injection in litellm https://github.com/advisories/GHSA-h6m6-jj8v-94jj Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed5.3LiteLLM CVE-2024-5710: Improper access control in litellm team management
Patch now · Disclosed · since 27 Jun 2024 · CVE-2024-5710
AI - closed9.8LiteLLM CVE-2024-5751: Remote code execution in litellm
Patch now · Disclosed · since 27 Jun 2024 · CVE-2024-5751
AI - closed7.0LiteLLM CVE-2024-4888: Arbitrary File Deletion in LiteLLM
Patch now · Disclosed · since 6 Jun 2024 · CVE-2024-4888
AI - closed8.1LiteLLM CVE-2025-0628: LiteLLM Improper Authorization and Privilege Escalation
Patch now · Disclosed · since 20 Mar 2025 · CVE-2025-0628
AI - closed5.8LocalAI CVE-2024-6095: SSRF and LFI vulnerability in LocalAI models apply endpoint
Patch now · Disclosed · since 6 Jul 2024 · CVE-2024-6095
AI - closed8.4LoLLMs CVE-2024-4897: RCE vulnerability in lollms-webui via insecure dependency
Patch now · Disclosed · since 2 Jul 2024 · CVE-2024-4897
AI