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

> Unauthenticated attackers can change admin passwords via the /_Passwd.html endpoint, leading to full system compromise of the TEX device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-ppm2-7rr7-h984

## What is CVE-2025-63207?

CVE-2025-63207 is a critical authentication bypass vulnerability in n/a, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The R.V.R Elettronica TEX product (firmware TEXL-000400, Web GUI TLAN-000400) is vulnerable to broken access control due to improper authentication checks on the /_Passwd.html endpoint. An attacker can send an unauthenticated POST request to change the Admin, Operator, and User passwords, resulting in complete system compromise.

Weakness: CWE-287 (Improper Authentication)

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

It affects 11 products.


Products: Rvr Tex1002lcd Firmware, Rvr Tex100lcd\/S Firmware, Rvr Tex150lcd\/S Firmware, Rvr Tex2000light Firmware, Rvr Tex2500lcd Firmware, Rvr Tex300lcd Firmware, Rvr Tex30lcd\/S Firmware, Rvr Tex3500lcd Firmware, Rvr Tex502lcd Firmware, Rvr Tex50lcd\/S Firmware, Rvr Tex702lcd Firmware.

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

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

## Is CVE-2025-63207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63207 is a critical authentication bypass vulnerability in n/a, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63207 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-63207/ (Markdown: https://insights.sbomify.com/CVE-2025-63207/index.md)
```

## Sources

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

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