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

> The gateway firmware displays the administrator password in plaintext on the web interface, allowing attackers to steal credentials and gain full control.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-3gw5-g9jg-7w5w

## What is CVE-2025-63361?

CVE-2025-63361 is a medium-severity vulnerability in n/a, published on 4 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### 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 render the Administrator password in plaintext.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


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

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

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

## Is CVE-2025-63361 being exploited?

There is no known exploitation of CVE-2025-63361 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-63364](https://insights.sbomify.com/CVE-2025-63364/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63361 is a medium-severity vulnerability in n/a, published on 4 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-63361 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-63361/ (Markdown: https://insights.sbomify.com/CVE-2025-63361/index.md)
```

## Sources

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

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