{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-46398 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46398 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46398 is a high-severity vulnerability in haxtheweb haxcms-php, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46398 and fix it if it is affected.\n\nWhat it is: CVE-2026-46398 is a high-severity vulnerability in haxtheweb haxcms-php, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46398 in the wild and no public exploit code.\n\nAffected product: haxtheweb haxcms-php. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46398/ (Markdown: https://insights.sbomify.com/CVE-2026-46398/index.md)","id":"CVE-2026-46398","markdown":"https://insights.sbomify.com/CVE-2026-46398/index.md","name":"CVE-2026-46398","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"HAX CMS","requires_auth":"none","summary":"Attackers can steal session tokens via network sniffing because the cookie lacks the Secure flag, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-614","name":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"HAX CMS Missing Secure Flag on Cookie","id":"CVE-2026-46398","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Authenticated Remote Code Execution via File Overwrite","id":"CVE-2026-46399"},"packages":[],"prev":{"headline":"haxcms-php Local File Inclusion via saveOutline API Location Parameter v2.0","id":"CVE-2026-46397"},"products":["haxcms-php"],"published":"2026-06-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-05","vendors":["haxtheweb"]},"summary":"Attackers can steal session tokens via network sniffing because the cookie lacks the Secure flag, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-46398/"}