CVE-2025-15107VulnerabilityPublished 27 Dec 2025Updated 29 Dec 2025

CVE-2025-15107: actiontech sqle · Use of Hard-coded Cryptographic Key

Affects actiontech sqleSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubactiontech/sqle`pkg:github/actiontech/sqle`Other threats	Affected =4.2511	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation should focus on reducing exposure of vulnerable sqle instances by restricting network access to trusted sources only, using firewalls or network segmentation. Organizations should monitor logs for suspicious JWT token activity or anomalies indicating token forgery attempts. Review and audit application code and deployment configurations to ensure no other hard-coded secrets exist. Once the vendor releases a patch, prioritize timely application of the update. Additionally, educate development teams on secure key management practices to avoid embedding static secrets in code. Employ runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block exploitation attempts targeting JWT handling. Finally, conduct penetration testing focused on JWT token security to identify potential exploitation paths.

Description

A security vulnerability has been detected in actiontech sqle up to 4.2511.0. The impacted element is an unknown function of the file sqle/utils/jwt.go of the component JWT Secret Handler. The manipulation of the argument JWTSecretKey leads to use of hard-coded cryptographic key . The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitability is regarded as difficult. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report and is planning to fix this flaw in an upcoming release.

Impact

For European organizations, the use of actiontech sqle version 4.2511.0 with this vulnerability could lead to unauthorized access if attackers manage to exploit the hard-coded JWT secret key. This could compromise sensitive data protected by JWT tokens, including user identities and session information, potentially leading to data breaches or privilege escalation. The medium severity rating reflects that while exploitation is difficult, the impact on confidentiality is significant. Organizations in sectors with strict data protection requirements, such as finance, healthcare, and government, may face regulatory and reputational risks if this vulnerability is exploited. Additionally, since the attack can be performed remotely without authentication, exposed sqle instances accessible over the network are at higher risk. The lack of known exploits in the wild currently reduces immediate threat but does not eliminate future risk, especially after public disclosure. European entities relying on JWT for authentication in sqle should consider this vulnerability a priority for remediation planning.

Summary

CVE-2025-15107 identifies a security vulnerability in the actiontech sqle product, specifically in versions up to 4.2511.0. The vulnerability resides in the JWT Secret Handler component, within the file sqle/utils/jwt.go, where a hard-coded cryptographic key (JWTSecretKey) is used. Hard-coded keys are a critical security flaw because they are static, predictable, and cannot be changed easily, which undermines the cryptographic strength of JWT tokens used for authentication or authorization. An attacker who can remotely interact with the system may exploit this flaw to decrypt, forge, or manipulate JWT tokens, potentially bypassing security controls or gaining unauthorized access. The attack vector is network-based (AV:N), does not require privileges (PR:N), authentication (AT:N), or user interaction (UI:N), but the attack complexity is high (AC:H), indicating that exploitation requires significant effort or specific conditions. The vulnerability impacts confidentiality (VC:L) but not integrity or availability. No known exploits have been observed in the wild, but public disclosure increases the risk of exploitation attempts. This vulnerability highlights the risks of embedding static cryptographic secrets in code, which is a poor security practice that can lead to token compromise and unauthorized access.

References

Community reviews

Loading reviews…