CVE-2026-46398
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.8
- CVSS vector
- 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
- EPSS probability
- 0.18%
- CWE
- CWE-614
- Published
- 2026-06-05
- Last modified
- 2026-06-05
Affected products
- haxtheweb haxcms-php
Weakness type
Related vulnerabilities
- CVE-2026-65655 — Temporal UI Server may set OAuth credential cookies without Secure behind a TLS-terminating reverse proxy
- CVE-2026-15656 — IBM MAS uses axios-1.15.2, protobufjs-8.0.1 and undici-7.26 which is vulnerable to multiple CVEs, and contains vulnerabilities related to missing Secure attribute on mas-redirect-uri cookie and weak HMAC Session Secret
- CVE-2026-48058 — nebula-mesh: Session and OIDC state cookies lack the Secure attribute
- CVE-2026-56581 — HCL MyCloud was affected with Cookie Attribute Path Not Set
- CVE-2024-23572 — HCL Aftermarket EPC is vulnerable to attack as cookie appears to contain a session token, which may...
- CVE-2026-57948 — Pinpoint - Insecure Session Cookie Attributes in pinpointJwt
- CVE-2026-46550 — NocoDB: Refresh Token Cookie Set Without `Secure` and `SameSite` Flags
- CVE-2026-53661 — boruta-server sent sensitive session cookies without the Secure attribute