# CVE-2025-54807: Dover Fueling Solutions ProGauge MagLink LX 4 Devices Use of Hard-coded Cryptographic Key

> Attackers can bypass authentication and gain full system access by exploiting a hardcoded cryptographic key in the device firmware.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 18 Sep 2025
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-fmx3-xgw6-w7g2

## What is CVE-2025-54807?

CVE-2025-54807 is a critical vulnerability in Dover Fueling Solutions ProGauge MagLink LX 4, published on 18 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The secret used for validating authentication tokens is hardcoded in 
device firmware for affected versions. An attacker who obtains the 
signing key can bypass authentication, gaining complete access to the 
system.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2025-54807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54807 is a critical vulnerability in Dover Fueling Solutions ProGauge MagLink LX 4, published on 18 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-54807 in the wild and no public exploit code.

Affected product: Dover Fueling Solutions ProGauge MagLink LX 4. 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-54807/ (Markdown: https://insights.sbomify.com/CVE-2025-54807/index.md)
```

## Sources

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

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