# CVE-2025-52389: Information disclosure in n/a

> Authenticated attackers can access other users' sensitive data via crafted HTTP requests in Soda Cristal.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-7pcv-82qf-g35c

## What is CVE-2025-52389?

CVE-2025-52389 is a high-severity vulnerability in n/a, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An Insecure Direct Object Reference (IDOR) in Envasadora H2O Eireli - Soda Cristal v40.20.4 allows authenticated attackers to access sensitive data for other users via a crafted HTTP request.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-52389 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52389 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52389 is a high-severity vulnerability in n/a, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52389 exists.

Affected product: n/a. 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-52389/ (Markdown: https://insights.sbomify.com/CVE-2025-52389/index.md)
```

## Sources

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

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