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

> Unauthenticated attackers can enumerate valid user accounts via distinguishable password reset responses, facilitating targeted attacks like password spraying.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2025
- **Updated:** 1 Oct 2025
- **Also known as:** GHSA-qjf7-p4pc-2mq7

## What is CVE-2025-56132?

CVE-2025-56132 is a high-severity vulnerability in n/a, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LiquidFiles filetransfer server is vulnerable to a user enumeration issue in its password reset functionality. The application returns distinguishable responses for valid and invalid email addresses, allowing unauthenticated attackers to determine the existence of user accounts. Version 4.2 introduces user-based lockout mechanisms to mitigate brute-force attacks, user enumeration remains possible by default. In versions prior to 4.2, no such user-level protection is in place, only basic IP-based rate limiting is enforced. This IP-based protection can be bypassed by distributing requests across multiple IPs (e.g., rotating IP or proxies). Effectively bypassing both login and password reset security controls. Successful exploitation allows an attacker to enumerate valid email addresses registered for the application, increasing the risk of follow-up attacks such as password spraying.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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

It affects 1 product.


Products: Liquidfiles Liquidfiles.

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

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

## Is CVE-2025-56132 being exploited?

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

Public exploit code:

- https://github.com/fredericgoossens/CVE-2025-56132-Liquidfiles (github_poc): https://github.com/fredericgoossens/CVE-2025-56132-Liquidfiles
- LiquidFiles < 4.2 - User Enumeration via Password Reset (nuclei): http/cves/2025/CVE-2025-56132.yaml

## Other vulnerabilities in n/a

- [CVE-2025-46093](https://insights.sbomify.com/CVE-2025-46093/): Privilege escalation in LiquidFiles (critical 9.9)
- [CVE-2020-29071](https://insights.sbomify.com/CVE-2020-29071/): Cross-site scripting in n/a (critical 9.0)
- [CVE-2021-43397](https://insights.sbomify.com/CVE-2021-43397/): LiquidFiles before 3.6.3 allows remote attackers to elevate their privileges from Admin (or User Admin) to Sysadmin. (high 8.8)
- [CVE-2020-29072](https://insights.sbomify.com/CVE-2020-29072/): Information disclosure in n/a (medium 6.1)
- [CVE-2023-4393](https://insights.sbomify.com/CVE-2023-4393/): HTML and SMTP Injection in LiquidFiles (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56132 is a high-severity vulnerability in n/a, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56132 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-56132/ (Markdown: https://insights.sbomify.com/CVE-2025-56132/index.md)
```

## Sources

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

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