# CVE-2025-54554: Information disclosure in tiCrypt

> Unauthenticated attackers can access sensitive SQL query and database structure information via the REST API in tiCrypt.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2025
- **Updated:** 5 Aug 2025
- **Also known as:** GHSA-jfm6-9g2x-f7pr

## What is CVE-2025-54554?

CVE-2025-54554 is a medium-severity vulnerability in Tera Insights tiCrypt, published on 4 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tiaudit in Tera Insights tiCrypt before 2025-07-17 allows unauthenticated REST API requests that reveal sensitive information about the underlying SQL queries and database structure.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-54554 being exploited?

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

Public exploit code:

- CVE-2025-54554 – Unauthenticated Access in tiaudit REST API leading to Sensitive Information Disclosure (github_poc): https://github.com/Aman-Parmar/CVE-2025-54554

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54554 is a medium-severity vulnerability in Tera Insights tiCrypt, published on 4 Aug 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-54554 in the wild and no public exploit code.

Affected product: Tera Insights tiCrypt. 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-54554/ (Markdown: https://insights.sbomify.com/CVE-2025-54554/index.md)
```

## Sources

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

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