Authentication bypass via hard-coded JWT signing key
Published Dec 27, 2025 · Updated Dec 27, 2025
Authentication bypass in ActionTech SQLE 4.2511.0 and earlier allows remote attackers to forge administrator JWTs. sqle/utils/jwt.go initializes JWTSecretKey to the constant "secret" and uses it to validate HS256 tokens, while authorization relies on the token's user identifier. No credentials or user interaction are required, but exploitation requires a valid token with a privileged identifier; successful use grants backend access.
Summary
What happened
Authentication bypass in ActionTech SQLE 4.2511.0 and earlier allows remote attackers to forge administrator JWTs. sqle/utils/jwt.go initializes JWTSecretKey to the constant "secret" and uses it to validate HS256 tokens, while authorization relies on the token's user identifier. No credentials or user interaction are required, but exploitation requires a valid token with a privileged identifier; successful use grants backend access.
The record
- CVE
- CVE-2025-15107
- Published
- Dec 27, 2025
- Updated
- Dec 27, 2025
- Vendor
- ActionTech
- Product
- SQLE
- Classifications
- CWE-321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2025CVE publishedPublication date reported by the CVE source.
- Dec 27, 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=4.2511
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
- SQLE hard-coded JWT proof of conceptproof of concept · demonstrated
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