# CVE-2025-3578: Adversarial Input Handling Vulnerability in AiDex

> Authenticated users can exploit LLM prompt injection to list credentials, modify users, and exfiltrate sensitive system information via the message endpoint.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-j2g7-67mh-m3hh

## What is CVE-2025-3578?

CVE-2025-3578 is a critical vulnerability in AiDex, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A malicious, authenticated user in Aidex, versions prior to 1.7, could list credentials of other users, create or modify existing users in the application, list credentials of users in production or development environments. In addition, it would be possible to cause bugs that would result in the exfiltration of sensitive information, such as details about the software or internal system paths. These actions could be carried out through the misuse of LLM Prompt (chatbot) technology, via the /api/<string-chat>/message endpoint, by manipulating the contents of the ‘content’ parameter.

Weakness: CWE-1039 (Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism)

## Which versions are affected by CVE-2025-3578?


## How do I fix CVE-2025-3578?

No fix has been published for CVE-2025-3578 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3578 being exploited?

There is no known exploitation of CVE-2025-3578 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3578 and fix it if it is affected.

What it is: CVE-2025-3578 is a critical vulnerability in AiDex, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3578 in the wild and no public exploit code.

Affected product: AiDex. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3578/ (Markdown: https://insights.sbomify.com/CVE-2025-3578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3578
- OSV: https://osv.dev/vulnerability/CVE-2025-3578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3578/
Summaries are generated and may contain mistakes; the official description above is the record.