# CVE-2024-58277: R Radio Network FM Transmitter 1.07 System Settings Disclosure

> Unauthenticated attackers can retrieve admin passwords via system.cgi, enabling authentication bypass and unauthorized access to FM station settings.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 14 May 2026
- **Also known as:** GHSA-q2q3-g3x6-pfhj

## What is CVE-2024-58277?

CVE-2024-58277 is a high-severity vulnerability in Radio Network FM Transmitter, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

R Radio Network FM Transmitter 1.07 allows unauthenticated attackers to access the admin user's password through the system.cgi endpoint, enabling authentication bypass and FM station setup access.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2024-58277?


## How do I fix CVE-2024-58277?

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

## Is CVE-2024-58277 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58277 and fix it if it is affected.

What it is: CVE-2024-58277 is a high-severity vulnerability in Radio Network FM Transmitter, published on 4 Dec 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-2024-58277 exists.

Affected product: Radio Network FM Transmitter. 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-2024-58277/ (Markdown: https://insights.sbomify.com/CVE-2024-58277/index.md)
```

## Sources

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

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