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.
Published: 2026-10-16
Score: 8.8 High
EPSS: n/a
KEV: No
Impact: Authentication Bypass
Action: Immediate Patch
AI Analysis

Impact

ZKEACMS version 4.4 contains a hard‑coded HMAC‑SHA256 signing key in JwtBearerDefaults.cs that allows an unauthenticated attacker to forge JWT bearer tokens. By creating a token with the Name claim set to "admin" the attacker can bypass authentication and gain administrator privileges to modify articles, products, and read form submissions. This represents a classic authentication bypass flaw described by CWE‑321, where predictable credentials or cryptographic secrets compromise the integrity of a system.

Affected Systems

The vulnerability affects the SeriaWei ZKEACMS product, specifically versions up to and including 4.4. Administrators running any deployment of ZKEACMS 4.4 or earlier are impacted and should verify their installed version.

Risk and Exploitability

The CVSS score of 8.8 classifies this as a high severity issue, indicating that successful exploitation provides complete control over protected resources. The EPSS score is not available, and the vulnerability is not listed in CISA KEV, suggesting that while it is high risk, the likelihood of widespread exploitation remains uncertain. The attack vector is inferred to be through the REST API, where an attacker can craft HTTP requests containing a forged JWT without needing any prior authentication.

Generated by OpenCVE AI on October 16, 2026 at 18:47 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade ZKEACMS to the latest version that removes the hard‑coded signing key.
  • If an upgrade is not immediately possible, replace the hard‑coded key in JwtBearerDefaults.cs with a unique, secret key that is generated per installation and stored securely.
  • Ensure that all API endpoints validate the JWT signature, issuer, and audience, and that the Name claim is only honored for properly authenticated users.

Generated by OpenCVE AI on October 16, 2026 at 18:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 17:45:00 +0000

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

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L'}

cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-16T17:39:06.226Z

Reserved: 2026-10-16T14:31:12.512Z

Link: CVE-2026-111633

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-10-16T18:17:43.607

Modified: 2026-10-16T19:04:35.840

Link: CVE-2026-111633

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T19:00:11Z

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key