Complete system access via hardcoded signing key
Published Sep 18, 2025 · Updated Sep 18, 2025
Authentication bypass in ProGauge MagLink LX 4 and LX Plus before 4.20.3 and LX Ultimate before 5.20.3 allows remote attackers complete system access. Device firmware embeds the secret used to validate authentication tokens, so a token signed with that key is accepted as authentic. Network reachability and possession of the signing key are required; successful forgery bypasses authentication and grants unrestricted control.
Summary
What happened
Authentication bypass in ProGauge MagLink LX 4 and LX Plus before 4.20.3 and LX Ultimate before 5.20.3 allows remote attackers complete system access. Device firmware embeds the secret used to validate authentication tokens, so a token signed with that key is accepted as authentic. Network reachability and possession of the signing key are required; successful forgery bypasses authentication and grants unrestricted control.
The record
- CVE
- CVE-2025-54807
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- Dover Fueling Solutions
- Product
- ProGauge MagLink LX Plus
- Classifications
- CWE-321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.20.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo