# CVE-2025-47818: Hardcoded credentials in Gunshot Detection devices

> Attackers can access Flock Safety Gunshot Detection devices using hard-coded credentials, potentially leading to unauthorized access and data exposure.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2025
- **Updated:** 2 Sep 2025
- **Also known as:** GHSA-6r23-52v3-r282

## What is CVE-2025-47818?

CVE-2025-47818 is a low-severity vulnerability in Flock Safety Gunshot Detection devices, published on 27 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Flock Safety Gunshot Detection devices before 1.3 have a hard-coded password for a connection.

Weakness: CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: Flocksafety Gunshot Detection Firmware.

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

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

## Is CVE-2025-47818 being exploited?

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

## Other vulnerabilities in Flock Safety Gunshot Detection devices

- [CVE-2025-47819](https://insights.sbomify.com/CVE-2025-47819/): Missing authorization in Gunshot Detection devices (medium 6.4)
- [CVE-2025-47821](https://insights.sbomify.com/CVE-2025-47821/): Hardcoded credentials in Gunshot Detection devices (low 2.2)
- [CVE-2025-47820](https://insights.sbomify.com/CVE-2025-47820/): Hardcoded credentials in Gunshot Detection devices (low 2.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47818 is a low-severity vulnerability in Flock Safety Gunshot Detection devices, published on 27 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47818 in the wild and no public exploit code.

Affected product: Flock Safety Gunshot Detection devices. 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-47818/ (Markdown: https://insights.sbomify.com/CVE-2025-47818/index.md)
```

## Sources

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

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