{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-46493 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46493 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46493 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-46493 and fix it if it is affected.\n\nWhat it is: CVE-2026-46493 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-46493 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-46493/ (Markdown: https://insights.sbomify.com/CVE-2026-46493/index.md)","id":"CVE-2026-46493","markdown":"https://insights.sbomify.com/CVE-2026-46493/index.md","name":"CVE-2026-46493","record":{"aliases":["GHSA-xg43-xm47-74cp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HAX CMS PHP","requires_auth":"none","summary":"HAX CMS PHP uses insecure salt generation, potentially allowing attackers to bypass security mechanisms or predict tokens.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"HAX CMS helps manage microsite universe with PHP or NodeJs backends. Versions prior to 26.0.1 use `uniqid` for generating salts, which is unsuitable. Version 26.0.1 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":false,"headline":"haxtheweb/haxcms-php uses insecure method for generating salt","id":"CVE-2026-46493","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OpenDJ Pre-Auth RCE via Java Deserialization in JMX RMI","id":"CVE-2026-46495"},"packages":[],"prev":{"headline":"md-fileserver: Stored/Reflected XSS when viewing Markdown (raw HTML allowed)","id":"CVE-2026-46492"},"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":"HAX CMS PHP uses insecure salt generation, potentially allowing attackers to bypass security mechanisms or predict tokens.","url":"https://insights.sbomify.com/CVE-2026-46493/"}