Technical impact
The vulnerability arises from a hardcoded default JWT secret embedded in ng-antd-admin prior to version 22.0. An attacker can forge JWT tokens by using this known secret, thereby bypassing authentication and achieving full privilege escalation. The direct consequence is that any user, including administrators, can be impersonated, leading to account takeover, data leakage, and unauthorized operations on protected APIs. This flaw is marked as CWE‑321, representing insecure cryptographic key management.
Affected Systems
Affected systems are deployments of the ng‑antd-admin Angular + NestJS administration template that have not overridden the default JWT secret. The security advisory states that all releases before v22.0 contain the hardcoded key. The 22.0 release rejects the shipped secret in production but still permits it in non‑production environments, producing a warning only. Therefore, any installation of an earlier version or a 22.0 build with default secret enabled in production remains vulnerable.
Risk and Exploitability
The CVSS score of 9.8 reflects the high severity of this flaw. Exploitation is trivial for anyone who can provide a forged JWT token to the application, so the attack vector is effectively remote network. The EPSS is not available, and the vulnerability is not listed in CISA KEV. An attacker does not need privileged access to the server; by simply crafting a token with the hardcoded secret and using it against any authenticated endpoint, full administrative control can be achieved. As a result, the risk is high and immediate action is recommended.