CVE-2026-46395
published 2026-06-05CVE-2026-46395: HAX CMS helps manage microsite universe with PHP or NodeJs backends. Prior to version 26.0.0, the `hmacBase64()` function in the HAXcms Node.js backend…
PriorityP261critical9.3CVSS 4.0
AVNACLATNPRNUINVCHVIHVAHSCNSINSANEXCRXIRXARXMAVXMACXMATXMPRXMUIXMVCXMVIXMVAXMSCXMSIXMSAXSXAUXRXVXREXUX
EPSS
0.29%
21.1th percentile
HAX CMS helps manage microsite universe with PHP or NodeJs backends. Prior to version 26.0.0, the `hmacBase64()` function in the HAXcms Node.js backend contains two critical cryptographic implementation errors that together allow any unauthenticated attacker to extract the system’s private signing key and forge arbitrary admin-level JSON Web Tokens (JWTs) allowing them to get full admin access with a single HTTP request. First, the function passes the literal string "0" as the HMAC signing key instead of the key parameter, making every HAXcms instance compute identical HMACs for the same input. Then, after computing the HMAC, the function concatenates the real key parameter which is "this.privateKey + this.salt", the system’s master signing secret is directly onto the output. The combined buffer is base64-encoded and returned as the token. Every base64url token produced has the same structure: 32 bytes HMAC keyed with "0" and N bytes of `privateKey+salt`. An attacker base64-decodes any token, discards the first 32 bytes, and reads the private key directly. The `/system/api/connectionSettings` endpoint is unauthenticated and returns multiple tokens generated by this function. A single GET request to this endpoint exposes the private key. The PHP backend implements this function correctly with the actual key and returns only the hash. The PHP version produces 44-character tokens whereas the broken Node.js version produces 139+ character tokens. Version 26.0.0 fixes the issue.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| haxtheweb | haxcms-nodejs | < 26.0.0 | 26.0.0 |
| haxtheweb | haxcms-nodejs | >= 0 < 26.0.0 | 26.0.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
haxtheweb haxcms-nodejs up to 25.x PHP Backend hmacBase64 key information disclosure (GHSA-6c8g-9hfh-pq5h)
vuldb·2026-06-05·CVSS 9.3
CVE-2026-46395 [CRITICAL] haxtheweb haxcms-nodejs up to 25.x PHP Backend hmacBase64 key information disclosure (GHSA-6c8g-9hfh-pq5h)
A vulnerability was found in haxtheweb haxcms-nodejs up to 25.x. It has been rated as problematic. This issue affects the function hmacBase64 of the component PHP Backend. This manipulation of the argument key causes information disclosure.
This vulnerability is tracked as CVE-2026-46395. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is advised.
GHSA
HAXcms: Private Key Disclosure via Broken HMAC Implementation
ghsa·2026-05-19
CVE-2026-46395 [CRITICAL] CWE-200 HAXcms: Private Key Disclosure via Broken HMAC Implementation
HAXcms: Private Key Disclosure via Broken HMAC Implementation
### Summary
The `hmacBase64()` function in the HAXcms Node.js backend contains two critical cryptographic implementation errors that together allow any unauthenticated attacker to extract the system’s private signing key and forge arbitrary admin-level JSON Web Tokens (JWTs) allowing them to get full admin access with a single HTTP request.
### Details
Bug 1: Hardcoded HMAC Key (line 2160): The function passes the literal string "0" as the HMAC signing key instead of the key parameter, making every HAXcms instance compute identical HMACs for the same input.
Bug 2: Private Key Appended to Output (lines 2161- 2163): After computing the HMAC, the function concatenates the real key parameter which is "this.privateKey + this.salt"
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-06-05
Published