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

> Unauthenticated attackers can retrieve plaintext admin credentials and system settings from the ELCA Star Transmitter firmware via an unprotected endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 19 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-p4c3-mv98-x49f

## What is CVE-2025-63209?

CVE-2025-63209 is a high-severity 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 ELCA Star Transmitter Remote Control firmware 1.25 for STAR150, BP1000, STAR300, STAR2000, STAR1000, STAR500, and possibly other models, contains an information disclosure vulnerability allowing unauthenticated attackers to retrieve admin credentials and system settings via an unprotected /setup.xml endpoint. The admin password is stored in plaintext under the <p05> XML tag, potentially leading to remote compromise of the transmitter system.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 6 products.


Products: Elcaradio Bp1000 Firmware, Elcaradio Star1000 Firmware, Elcaradio Star150 Firmware, Elcaradio Star2000 Firmware, Elcaradio Star300 Firmware, Elcaradio Star500 Firmware.

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

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

## Is CVE-2025-63209 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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