ZKEACMS through 4.4 Authentication Bypass via Hard-Coded JWT Signing Key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| SeriaWei | ZKEACMS | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Seriawei | Zkeacms |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.439% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Seriawei
Seriawei zkeacms |
|
| Vendors & Products |
Seriawei
Seriawei zkeacms |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ZKEACMS through 4.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge REST API JWT bearer tokens using a hard-coded HMAC-SHA256 signing key in JwtBearerDefaults.cs. Attackers can sign a token with the Name claim set to 'admin' to call ApiAuthorize endpoints, modifying articles and products and reading form submissions. | |
| Title | ZKEACMS through 4.4 Authentication Bypass via Hard-Coded JWT Signing Key | |
| Weaknesses | CWE-321 | |
| References |
|
|
| Metrics |
cvssV3_1
|