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

> Local attackers can access the UART console without authentication to read boot sequences and reveal sensitive system information.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-pwv6-v269-632r

## What is CVE-2025-44039?

CVE-2025-44039 is a medium-severity vulnerability in n/a, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CP-XR-DE21-S -4G Router Firmware version 1.031.022 was discovered to contain insecure protections for its UART console. This vulnerability allows local attackers to connect to the UART port via a serial connection, read all boot sequence, and revealing internal system details and sensitive information without any authentication.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Cpplusworld Cp-Xr-De21-S Firmware.

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

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

## Is CVE-2025-44039 being exploited?

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

Public exploit code:

- This report is for CVE-2025-44039 reserved for Router UART vulnerability assigned to Discoverer Yashodhan Vivek Mandke. Please download the report pdf in this repositoy (github_poc): https://github.com/Yashodhanvivek/CP-XR-DE21-S--4G-Router-Vulnerabilities

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44039 is a medium-severity vulnerability in n/a, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44039 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-44039/ (Markdown: https://insights.sbomify.com/CVE-2025-44039/index.md)
```

## Sources

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

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