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

> An attacker can access sensitive information via the /FrameSetCore.html endpoint in Electrolink DAB transmitter web management systems.

- **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:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-5v2x-grvj-v7m2

## What is CVE-2025-51040?

CVE-2025-51040 is a high-severity vulnerability in n/a, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Electrolink FM/DAB/TV Transmitter Web Management System Unauthorized access vulnerability via the /FrameSetCore.html endpoint in Electrolink 500W, 1kW, 2kW Medium DAB Transmitter Web v01.09, v01.08, v01.07, and Display v1.4, v1.2.

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

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

It affects 1 product.


Products: Electrolink Fm\/Dab\/Tv Transmitter Web Management System.

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

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

## Is CVE-2025-51040 being exploited?

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

Public exploit code:

- There is a POC for CVE-2025-51040 in Electrolink FM/DAB/TV Transmitter Web Management System Unauthorized access vulnerability (github_poc): https://github.com/p0et08/Electrolink-FM-DAB-TV

## Other vulnerabilities in n/a

- [CVE-2025-28228](https://insights.sbomify.com/CVE-2025-28228/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51040 is a high-severity vulnerability in n/a, published on 6 Aug 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-51040 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-51040/ (Markdown: https://insights.sbomify.com/CVE-2025-51040/index.md)
```

## Sources

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

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