CVE-2026-46398: haxtheweb haxcms-php · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Affects haxtheweb haxcms-phpSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 26.0.0 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade haxcms-php and haxtheweb/haxcms-php to 26.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| haxthewebhaxcms-php | Affected
| Fixed in
|
GitHubhaxtheweb/haxcms-phppkg:github/haxtheweb/haxcms-phpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade haxcms-php to version 26.0.0 or later, where the haxcms_refresh_token cookie is set with the Secure attribute. This official fix ensures the cookie is only transmitted over encrypted HTTPS connections, mitigating the risk of interception. Until the upgrade is applied, avoid using unencrypted HTTP connections to access the application to reduce exposure.
Description
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.