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

> Attackers can bypass authentication on Newtec Celox UHD devices by forging login responses, gaining Superuser or Operator access without valid credentials.

- **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:** 19 Nov 2025
- **Also known as:** GHSA-m3w6-c4j9-5c65

## What is CVE-2025-63210?

CVE-2025-63210 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 Newtec Celox UHD (models: CELOXA504, CELOXA820) running firmware version celox-21.6.13 is vulnerable to an authentication bypass. An attacker can exploit this issue by modifying intercepted responses from the /celoxservice endpoint. By injecting a forged response body during the loginWithUserName flow, the attacker can gain Superuser or Operator access without providing valid credentials.

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm), CWE-302 (Authentication Bypass by Assumed-Immutable Data), CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Newtec Celoxa504 Firmware, Newtec Celoxa820 Firmware.

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

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

## Is CVE-2025-63210 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63210 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-63210 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-63210/ (Markdown: https://insights.sbomify.com/CVE-2025-63210/index.md)
```

## Sources

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

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