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

> Attackers can intercept plaintext credentials and control data via man-in-the-middle attacks on Tinxy WiFi Lock Controllers.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-pw25-rj5h-xh7p

## What is CVE-2025-44612?

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

### Official description

Tinxy WiFi Lock Controller v1 RF was discovered to transmit sensitive information in plaintext, including control information and device credentials, allowing attackers to possibly intercept and access sensitive information via a man-in-the-middle attack.

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

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

It affects 1 product.


Products: Tinxy Wifi Lock Controller V1 Rf Firmware.

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

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

## Is CVE-2025-44612 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-44619](https://insights.sbomify.com/CVE-2025-44619/): Misconfiguration in n/a (critical 9.1)
- [CVE-2025-44614](https://insights.sbomify.com/CVE-2025-44614/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44612 is a medium-severity vulnerability in n/a, published on 30 May 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-44612 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-44612/ (Markdown: https://insights.sbomify.com/CVE-2025-44612/index.md)
```

## Sources

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

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