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

> The gateway firmware transmits administrator credentials in plaintext, allowing attackers to intercept them and gain unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-hf8c-hwqf-v6q3

## What is CVE-2025-63364?

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

### Official description

Waveshare RS232/485 TO WIFI ETH (B) Serial to Ethernet/Wi-Fi Gateway Firmware V3.1.1.0: HW 4.3.2.1: Webpage V7.04T.07.002880.0301 was discovered to transmit Administrator credentials in plaintext.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Waveshare Rs232\/485 to Wifi Eth \(B\) Firmware.

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

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

## Is CVE-2025-63364 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63362](https://insights.sbomify.com/CVE-2025-63362/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-63363](https://insights.sbomify.com/CVE-2025-63363/): Security feature bypass in n/a (high 7.5)
- [CVE-2025-63361](https://insights.sbomify.com/CVE-2025-63361/): Information disclosure in n/a (medium 5.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63364 is a high-severity vulnerability in n/a, published on 4 Dec 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-63364 in the wild and no public exploit code.

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-63364/ (Markdown: https://insights.sbomify.com/CVE-2025-63364/index.md)
```

## Sources

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

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