nocobase up to 1.9.4/2.0.0-alpha.37 JWT Service jwt-service.ts API_KEY hard-coded key

Summaryinfo

A vulnerability was found in nocobase up to 1.9.4/2.0.0-alpha.37. It has been rated as problematic. The impacted element is an unknown function of the file nocobase\packages\core\auth\src\base\jwt-service.ts of the component JWT Service. This manipulation of the argument API_KEY causes hard-coded key. This vulnerability appears as CVE-2025-13877. The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability was found in nocobase up to 1.9.4/2.0.0-alpha.37. It has been declared as problematic. Affected by this vulnerability is an unknown function of the file nocobase\packages\core\auth\src\base\jwt-service.ts of the component JWT Service. The manipulation of the argument API_KEY with an unknown input leads to a hard-coded key vulnerability. The CWE definition for the vulnerability is CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. As an impact it is known to affect confidentiality, integrity, and availability.

The advisory is shared at gist.github.com. This vulnerability is known as CVE-2025-13877. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

It is possible to download the exploit at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-200266). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• nocobase

Version

• 1.9.0
• 1.9.1
• 1.9.2
• 1.9.3
• 1.9.4
• 2.0.0-alpha.0
• 2.0.0-alpha.1
• 2.0.0-alpha.2
• 2.0.0-alpha.3
• 2.0.0-alpha.4
• 2.0.0-alpha.5
• 2.0.0-alpha.6
• 2.0.0-alpha.7
• 2.0.0-alpha.8
• 2.0.0-alpha.9
• 2.0.0-alpha.10
• 2.0.0-alpha.11
• 2.0.0-alpha.12
• 2.0.0-alpha.13
• 2.0.0-alpha.14
• 2.0.0-alpha.15
• 2.0.0-alpha.16
• 2.0.0-alpha.17
• 2.0.0-alpha.18
• 2.0.0-alpha.19
• 2.0.0-alpha.20
• 2.0.0-alpha.21
• 2.0.0-alpha.22
• 2.0.0-alpha.23
• 2.0.0-alpha.24
• 2.0.0-alpha.25
• 2.0.0-alpha.26
• 2.0.0-alpha.27
• 2.0.0-alpha.28
• 2.0.0-alpha.29
• 2.0.0-alpha.30
• 2.0.0-alpha.31
• 2.0.0-alpha.32
• 2.0.0-alpha.33
• 2.0.0-alpha.34
• 2.0.0-alpha.35
• 2.0.0-alpha.36
• 2.0.0-alpha.37

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #692205: https://github.com/nocobase https://github.com/nocobase/nocobase Latest Authorization Bypass (by 28Hus)

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion