# CVE-2025-48046: MICI Network Co. Ltd. NetFax Server Disclosure of Stored Passwords in Cleartext

> An authenticated user can retrieve the cleartext password of a configured SMTP server via an HTTP GET request to the config endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2025
- **Updated:** 5 Sep 2025
- **Also known as:** GHSA-hfcm-596p-c7f7

## What is CVE-2025-48046?

CVE-2025-48046 is a medium-severity vulnerability in MICI Network Co. Ltd. NetFax Server, published on 29 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated user can disclose the cleartext password of a configured SMTP server via an HTTP GET request to the /config.php endpoint.

Weakness: CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2025-48046 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48046 is a medium-severity vulnerability in MICI Network Co. Ltd. NetFax Server, published on 29 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48046 exists.

Affected product: MICI Network Co. Ltd. NetFax Server. 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-48046/ (Markdown: https://insights.sbomify.com/CVE-2025-48046/index.md)
```

## Sources

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

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