# CVE-2025-28201: Auth bypass in n/a

> Physically proximate attackers can execute arbitrary code or gain root access on the Victure RX1800 device.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 9 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-4hrx-7c6v-v9v5

## What is CVE-2025-28201?

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

### Official description

An issue in Victure RX1800 EN_V1.0.0_r12_110933 allows physically proximate attackers to execute arbitrary code or gain root access.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Govicture Rx1800 Firmware.

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

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

## Is CVE-2025-28201 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28200](https://insights.sbomify.com/CVE-2025-28200/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-28202](https://insights.sbomify.com/CVE-2025-28202/): Missing authorization in n/a (high 8.8)
- [CVE-2025-28203](https://insights.sbomify.com/CVE-2025-28203/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28201 is a medium-severity authentication bypass vulnerability in n/a, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-28201 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-28201/ (Markdown: https://insights.sbomify.com/CVE-2025-28201/index.md)
```

## Sources

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

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