# CVE-2025-5310: Dover Fueling Solutions ProGauge MagLink LX Consoles Missing Authentication for Critical Function

> Attackers can remotely create, delete, or modify files via an unauthenticated interface, potentially leading to remote code execution on fueling consoles.

- **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:** 27 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-gp8x-529h-7cmw

## What is CVE-2025-5310?

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

### Official description

Dover Fueling Solutions ProGauge MagLink LX Consoles expose an undocumented and unauthenticated target communication framework (TCF) interface on a specific port. Files can be created, deleted, or modified, potentially leading to remote code execution.

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

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


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

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

## Is CVE-2025-5310 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5310 is a critical missing authorization vulnerability in Dover Fueling Solutions ProGauge MagLink LX 4, published on 27 Jun 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-5310 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-5310/ (Markdown: https://insights.sbomify.com/CVE-2025-5310/index.md)
```

## Sources

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

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