Authentication bypass via hard-coded JWT secret
Published Aug 26, 2025 · Updated Aug 26, 2025
Hard-coded key use in Welotec egOS WebGUI before 1.7.7 and 1.8.0 through 1.8.1 allows remote attackers to bypass authentication. The backend embeds an HS256 JWT secret that the default user can read, allowing forged tokens to pass signature checks and reach protected API endpoints. No credentials or user interaction are required over a reachable network interface, and a forged token grants the protected API privileges encoded in it.
Summary
What happened
Hard-coded key use in Welotec egOS WebGUI before 1.7.7 and 1.8.0 through 1.8.1 allows remote attackers to bypass authentication. The backend embeds an HS256 JWT secret that the default user can read, allowing forged tokens to pass signature checks and reach protected API endpoints. No credentials or user interaction are required over a reachable network interface, and a forged token grants the protected API privileges encoded in it.
The record
- CVE
- CVE-2025-41702
- Published
- Aug 26, 2025
- Updated
- Aug 26, 2025
- Vendor
- Welotec
- Product
- EG500 Mk2 Headless
- Classifications
- CWE-321, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 26, 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.0.0 <<v1.7.7
- Affected versionversion=v1.8.0 <v1.8.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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