# CVE-2025-63225: Missing authorization in n/a

> Remote attackers can bypass authentication to modify configurations, upload firmware, and fully compromise the Eurolab ELTS100 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:** 18 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-jc9r-v5h3-q7gw

## What is CVE-2025-63225?

CVE-2025-63225 is a critical missing authorization vulnerability in n/a, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Eurolab ELTS100_UBX device (firmware version ELTS100v1.UBX) is vulnerable to Broken Access Control due to missing authentication on critical administrative endpoints. Attackers can directly access and modify sensitive system and network configurations, upload firmware, and execute unauthorized actions without any form of authentication. This vulnerability allows remote attackers to fully compromise the device, control its functionality, and disrupt its operation.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Eurolab-Srl Elts 100 Firmware.

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

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

## Is CVE-2025-63225 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63225 is a critical missing authorization vulnerability in n/a, published on 18 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-63225 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-63225/ (Markdown: https://insights.sbomify.com/CVE-2025-63225/index.md)
```

## Sources

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

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