Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 5 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,762exploited flaws on CISA’s list
34added in the last 30 days
324new WordPress flaws this week
390,007entries in the database

15 results

  • Mar 20, 2025An improper authorization vulnerability exists in the main-latest version of BerriAI/litellm.CVE-2025-0628 · Other software · berriai · reported by security@huntr.devHigh 8.1

    An improper authorization vulnerability exists in the main-latest version of BerriAI/litellm. When a user with the role 'internal_user_viewer' logs into the application, they are provided with an overly privileged API key. This key can be used to access all the admin functionality of the application, including endpoints such as '/users/list' and '/users/get_users'. This vulnerability allows for privilege escalation within the application, enabling any account to become a PROXY ADMIN.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 20, 2025In berriai/litellm version v1.52.1, an issue in proxy_server.py causes the leakage of Langfuse API keys when an error occurs while parsing team settings.CVE-2025-0330 · Other software · berriai · reported by security@huntr.devHigh 7.5

    In berriai/litellm version v1.52.1, an issue in proxy_server.py causes the leakage of Langfuse API keys when an error occurs while parsing team settings. This vulnerability exposes sensitive information, including langfuse_secret and langfuse_public_key, which can provide full access to the Langfuse project storing all requests.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 20, 2025In berriai/litellm before version 1.44.12, the `litellm/litellm_core_utils/litellm_logging.py` file contains a vulnerability where the API key masking code onlyCVE-2024-9606 · Other software · berriai · reported by security@huntr.devHigh 7.5

    In berriai/litellm before version 1.44.12, the `litellm/litellm_core_utils/litellm_logging.py` file contains a vulnerability where the API key masking code only masks the first 5 characters of the key. This results in the leakage of almost the entire API key in the logs, exposing a significant amount of the secret key. The issue affects version v1.44.9.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 20, 2025A Denial of Service (DoS) vulnerability exists in berriai/litellm version v1.44.5.CVE-2024-8984 · Other software · berriai · reported by security@huntr.devHigh 7.5

    A Denial of Service (DoS) vulnerability exists in berriai/litellm version v1.44.5. This vulnerability can be exploited by appending characters, such as dashes (-), to the end of a multipart boundary in an HTTP request. The server continuously processes each character, leading to excessive resource consumption and rendering the service unavailable. The issue is unauthenticated and does not require any user interaction, impacting all users of the service.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 20, 2025BerriAI/litellm version 1.40.12 contains a vulnerability that allows remote code execution.CVE-2024-6825 · Other software · berriai · reported by security@huntr.devHigh 8.8

    BerriAI/litellm version 1.40.12 contains a vulnerability that allows remote code execution. The issue exists in the handling of the 'post_call_rules' configuration, where a callback function can be added. The provided value is split at the final '.' mark, with the last part considered the function name and the remaining part appended with the '.py' extension and imported. This allows an attacker to set a system method, such as 'os.system', as a callback, enabling the execution of arbitrary commands when a chat response is processed.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 20, 2025A vulnerability in BerriAI/litellm, as of commit 26c03c9, allows unauthenticated users to cause a Denial of Service (DoS) by exploiting the use of ast.literal_eCVE-2024-10188 · Other software · berriai · reported by security@huntr.devHigh 7.5

    A vulnerability in BerriAI/litellm, as of commit 26c03c9, allows unauthenticated users to cause a Denial of Service (DoS) by exploiting the use of ast.literal_eval to parse user input. This function is not safe and is prone to DoS attacks, which can crash the litellm Python server.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 13, 2024A Server-Side Request Forgery (SSRF) vulnerability exists in berriai/litellm version 1.38.10.CVE-2024-6587 · Other software · berriai · reported by security@huntr.devHigh 7.5

    A Server-Side Request Forgery (SSRF) vulnerability exists in berriai/litellm version 1.38.10. This vulnerability allows users to specify the `api_base` parameter when making requests to `POST /chat/completions`, causing the application to send the request to the domain specified by `api_base`. This request includes the OpenAI API key. A malicious user can set the `api_base` to their own domain and intercept the OpenAI API key, leading to unauthorized access and potential misuse of the API key.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 27, 2024BerriAI/litellm version v1.35.8 contains a vulnerability where an attacker can achieve remote code execution.CVE-2024-5751 · Other software · berriai · reported by security@huntr.devCritical 9.8

    BerriAI/litellm version v1.35.8 contains a vulnerability where an attacker can achieve remote code execution. The vulnerability exists in the `add_deployment` function, which decodes and decrypts environment variables from base64 and assigns them to `os.environ`. An attacker can exploit this by sending a malicious payload to the `/config/update` endpoint, which is then processed and executed by the server when the `get_secret` function is triggered. This requires the server to use Google KMS and a database to store a model.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 27, 2024berriai/litellm version 1.34.34 is vulnerable to improper access control in its team management functionality.CVE-2024-5710 · Other software · berriai · reported by security@huntr.devMedium 6.5

    berriai/litellm version 1.34.34 is vulnerable to improper access control in its team management functionality. This vulnerability allows attackers to perform unauthorized actions such as creating, updating, viewing, deleting, blocking, and unblocking any teams, as well as adding or deleting any member to or from any teams. The vulnerability stems from insufficient access control checks in various team management endpoints, enabling attackers to exploit these functionalities without proper authorization.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 6, 2024An SQL Injection vulnerability exists in the berriai/litellm repository, specifically within the `/global/spend/logs` endpoint.CVE-2024-5225 · Other software · berriai · reported by security@huntr.devHigh 7.2

    An SQL Injection vulnerability exists in the berriai/litellm repository, specifically within the `/global/spend/logs` endpoint. The vulnerability arises due to improper neutralization of special elements used in an SQL command. The affected code constructs an SQL query by concatenating an unvalidated `api_key` parameter directly into the query, making it susceptible to SQL Injection if the `api_key` contains malicious data. This issue affects the latest version of the repository. Successful exploitation of this vulnerability could lead to unauthorized access, data manipulation, exposure of confidential information, and denial of service (DoS).

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 6, 2024A blind SQL injection vulnerability exists in the berriai/litellm application, specifically within the '/team/update' process.CVE-2024-4890 · Other software · berriai · reported by security@huntr.devMedium 4.9

    A blind SQL injection vulnerability exists in the berriai/litellm application, specifically within the '/team/update' process. The vulnerability arises due to the improper handling of the 'user_id' parameter in the raw SQL query used for deleting users. An attacker can exploit this vulnerability by injecting malicious SQL commands through the 'user_id' parameter, leading to potential unauthorized access to sensitive information such as API keys, user information, and tokens stored in the database. The affected version is 1.27.14.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 6, 2024BerriAI's litellm, in its latest version, is vulnerable to arbitrary file deletion due to improper input validation on the `/audio/transcriptions` endpoint.CVE-2024-4888 · Other software · berriai · reported by security@huntr.devHigh 8.1

    BerriAI's litellm, in its latest version, is vulnerable to arbitrary file deletion due to improper input validation on the `/audio/transcriptions` endpoint. An attacker can exploit this vulnerability by sending a specially crafted request that includes a file path to the server, which then deletes the specified file without proper authorization or validation. This vulnerability is present in the code where `os.remove(file.filename)` is used to delete a file, allowing any user to delete critical files on the server such as SSH keys, SQLite databases, or configuration files.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 6, 2024A code injection vulnerability exists in the berriai/litellm application, version 1.34.6, due to the use of unvalidated input in the eval function within the seCVE-2024-4889 · Other software · berriai · reported by security@huntr.devHigh 7.2

    A code injection vulnerability exists in the berriai/litellm application, version 1.34.6, due to the use of unvalidated input in the eval function within the secret management system. This vulnerability requires a valid Google KMS configuration file to be exploitable. Specifically, by setting the `UI_LOGO_PATH` variable to a remote server address in the `get_image` function, an attacker can write a malicious Google KMS configuration file to the `cached_logo.jpg` file. This file can then be used to execute arbitrary code by assigning malicious code to the `SAVE_CONFIG_TO_DB` environment variable, leading to full system control. The vulnerability is contingent upon the use of the Google KMS feature.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 17, 2024A remote code execution (RCE) vulnerability exists in the berriai/litellm project due to improper control of the generation of code when using the `eval` functiCVE-2024-4264 · Other software · berriai · reported by security@huntr.devCritical 9.8

    A remote code execution (RCE) vulnerability exists in the berriai/litellm project due to improper control of the generation of code when using the `eval` function unsafely in the `litellm.get_secret()` method. Specifically, when the server utilizes Google KMS, untrusted data is passed to the `eval` function without any sanitization. Attackers can exploit this vulnerability by injecting malicious values into environment variables through the `/config/update` endpoint, which allows for the update of settings in `proxy_server_config.yaml`.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 10, 2024BerriAI/litellm is vulnerable to Server-Side Template Injection (SSTI) via the `/completions` endpoint.CVE-2024-2952 · Other software · berriai · reported by security@huntr.devCritical 9.8

    BerriAI/litellm is vulnerable to Server-Side Template Injection (SSTI) via the `/completions` endpoint. The vulnerability arises from the `hf_chat_template` method processing the `chat_template` parameter from the `tokenizer_config.json` file through the Jinja template engine without proper sanitization. Attackers can exploit this by crafting malicious `tokenizer_config.json` files that execute arbitrary code on the server.

    Product
    berriai/litellm
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.