Skip to main content

CVE-2026-111633: Use of Hard-coded Cryptographic Key in SeriaWei ZKEACMS

0
High
VulnerabilityCVE-2026-111633cvecve-2026-111633
Published: 10/16/2026 (10/16/2026, 17:39:06 UTC)
Source: CVE Database V5
Vendor/Project: SeriaWei
Product: ZKEACMS

Description

ZKEACMS versions up to 4.4 contain an authentication bypass vulnerability due to a hard-coded cryptographic key used for signing JWT bearer tokens. This flaw allows unauthenticated attackers to forge tokens with administrative privileges, enabling modification of articles and products and access to form submissions.

CVSS v4.0

Score 8.8high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
Low
Vuln. Integrity
High
Vuln. Availability
Low
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

SeriaWei

ZKEACMS

Affected versions
>=0 <=4.4
GitHub Actionsmore threats →cve
ZKEACMS
pkg:github/ZKEACMS
Affected versions
>=0 <=4.4

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/16/2026, 18:48:22 UTC

Technical Analysis

CVE-2026-111633 describes a vulnerability in SeriaWei's ZKEACMS through version 4.4 where a hard-coded HMAC-SHA256 signing key in JwtBearerDefaults.cs enables attackers to forge JWT bearer tokens. By crafting a token with the Name claim set to 'admin', attackers can bypass authentication and invoke ApiAuthorize endpoints, leading to unauthorized modification and data access.

Potential Impact

The vulnerability allows unauthenticated attackers to gain administrative access to the CMS REST API, resulting in unauthorized modification of content (articles and products) and unauthorized reading of form submissions. This compromises the integrity and confidentiality of the system's data.

Mitigation Recommendations

No patch or official fix information is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the API endpoints and monitor for suspicious token usage if possible.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-10-16T14:31:12.512Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad2640e2cdf04f656199561

Added to database: 10/16/2026, 17:51:10 UTC

Last enriched: 10/16/2026, 18:48:22 UTC

Last updated: 10/16/2026, 19:03:25 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses