CVE-2025-9994
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Amp'ed RF BT-AP 111 Bluetooth access point's HTTP admin interface lacks authentication mechanisms, permitting any network-connected user to access administrative functions without credentials. This unauthenticated access yields full control over the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, packaging, or network discovery for 'Amp'ed RF BT-AP 111' or 'BT-AP 111' to confirm the device model matches the affected product.Affected if The device is an Amp'ed RF BT-AP 111 Bluetooth access point.
-
Locate the HTTP admin interfaceAccess the device's IP address on common HTTP ports (80, 8080, 8000) or check the device documentation for the admin URL. Attempt to reach the web interface over HTTP.Affected if The HTTP admin interface is reachable and responds to requests.
-
Test for authentication requirementAttempt to access administrative functions (such as device settings, configuration pages, or status dashboards) without providing any credentials. Observe whether the interface allows access or redirects to a login page.Affected if Administrative functions are accessible without any username or password prompt.
-
Check network exposureDetermine whether the device's admin interface is accessible from untrusted network segments (such as guest networks, public networks, or the internet) rather than being restricted to a trusted management VLAN.Affected if The admin interface is exposed to untrusted network segments without firewall or access control restrictions.
The environment is affected if an Amp'ed RF BT-AP 111 device has its HTTP admin interface accessible without authentication credentials from the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to the admin interface via firewall rules or network segmentation to prevent external/untrusted access; if vendor firmware with authentication is available, apply it immediately.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9994 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data