# CVE-2025-9994: Amp’ed RF BT-AP 111 Bluetooth access point's HTTP admin interface does not require authentication

> The Bluetooth access point's HTTP admin interface lacks authentication, allowing unauthorized network users to access administrative functions.

- **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:** 9 Sep 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-866h-762v-8qww

## What is CVE-2025-9994?

CVE-2025-9994 is a critical missing authorization vulnerability in Amped RF BT-AP 111, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Amp’ed RF BT-AP 111 Bluetooth access point's HTTP admin interface does not have an authentication feature, allowing unauthorized access to anyone with network access.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-9994 being exploited?

There is no known exploitation of CVE-2025-9994 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9994 is a critical missing authorization vulnerability in Amped RF BT-AP 111, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9994 in the wild and no public exploit code.

Affected product: Amped RF BT-AP 111. 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-9994/ (Markdown: https://insights.sbomify.com/CVE-2025-9994/index.md)
```

## Sources

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

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