Skip to main content

HAX CMS CVE-2026-46398

| EUVD-2026-34893 HIGH
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614)
2026-06-05 GitHub_M
8.8
CVSS 4.0 · GitHub Advisory
Share

Severity by source

GitHub Advisory PRIMARY
8.8 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
X

Lifecycle Timeline

4
Analysis Generated
Jun 05, 2026 - 21:50 vuln.today
Patch available
Jun 05, 2026 - 21:01 EUVD
CVSS changed
Jun 05, 2026 - 20:22 NVD
8.8 (HIGH)
CVE Published
Jun 05, 2026 - 19:13 nvd
UNKNOWN (no severity yet)

DescriptionGitHub Advisory

HAX CMS helps manage microsite universe with PHP or NodeJs backends. Starting in version 25.0.0 and prior to version 26.0.0, the haxcms_refresh_token cookie is set without the Secure flag. This allows it to be transmitted over unencrypted HTTP, making it vulnerable to theft via packet sniffing on the network. Version 26.0.0 fixes the issue.

AnalysisAI

Session token disclosure in HAX CMS versions 25.0.0 through 26.0.0 (exclusive) stems from the haxcms_refresh_token cookie being issued without the Secure flag, allowing the browser to send it over plaintext HTTP. A network-positioned attacker can capture the refresh token via passive sniffing and hijack the victim's authenticated session. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Position on shared network segment
Delivery
Wait for victim HTTP request to HAX CMS
Exploit
Sniff cleartext refresh token cookie
Execution
Replay token to issue new session
Impact
Authenticate as victim and access content

Vulnerability AssessmentAI

Exploitation Exploitation requires three concrete conditions: (1) the attacker must have a network observation point on the path between the victim browser and the HAX CMS server (same Wi-Fi segment, switch-span access, ISP-level MITM, or compromised upstream router); (2) the victim must transmit at least one HTTP (not HTTPS) request to the HAX CMS origin while holding a valid haxcms_refresh_token, which happens on plaintext redirects, mixed-content loads, or direct http:// navigation; and (3) the deployment must be reachable over HTTP at all - sites that only listen on 443 and enforce HSTS preload effectively block the leak path even on vulnerable versions. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment Signals point in conflicting directions and the CVSS 4.0 score of 8.8 is likely overstated for typical deployments. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario A user on an untrusted network (coffee shop Wi-Fi, conference LAN, hostile ISP) authenticates to a HAX CMS site, then later triggers any cleartext HTTP request to the same origin - for example, typing the bare domain into the address bar without https://, clicking an http:// link, or loading a mixed-content resource. An attacker passively sniffing the segment captures the haxcms_refresh_token in the request headers and replays it from their own client to obtain a valid authenticated session as the victim. …
Remediation Vendor-released patch: upgrade to HAX CMS 26.0.0, which sets the Secure flag on the haxcms_refresh_token cookie per GitHub Security Advisory GHSA-g7v2-r32q-jf5v (https://github.com/haxtheweb/issues/security/advisories/GHSA-g7v2-r32q-jf5v). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Inventory all HAX CMS instances and identify systems running versions 25.0.0 through 26.0.0 (exclusive). …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-46398 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy