{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35185 exists.","fix":"No fix has been published for CVE-2026-35185 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35185 is a high-severity vulnerability in haxtheweb HAXiam, published on 6 Apr 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-35185 and fix it if it is affected.\n\nWhat it is: CVE-2026-35185 is a high-severity vulnerability in haxtheweb HAXiam, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35185 exists.\n\nAffected product: haxtheweb HAXiam. 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-35185/ (Markdown: https://insights.sbomify.com/CVE-2026-35185/index.md)","id":"CVE-2026-35185","markdown":"https://insights.sbomify.com/CVE-2026-35185/index.md","name":"CVE-2026-35185","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HAX CMS","requires_auth":"none","summary":"Unauthenticated attackers can access the public /server-status endpoint to steal authentication tokens and monitor user activity in HAX CMS.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"haxiam","vendor":"psu"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"HAX CMS helps manage microsite universe with PHP or NodeJs backends. Prior to 25.0.0, the /server-status endpoint is publicly accessible and exposes sensitive information including authentication tokens (user_token), user activity, client IP addresses, and server configuration details. This allows any unauthenticated user to monitor real-time user interactions and gather internal infrastructure information. This vulnerability is fixed in 25.0.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"HAX CMS's public /server-status endpoint exposes authentication tokens, user activity, and client IP addresses","id":"CVE-2026-35185","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":"Wasmtime has an improperly masked return value from `table.grow` with Winch compiler backend","id":"CVE-2026-35186"},"packages":[],"prev":{"headline":"EcclesiaCRM has a Critical SQL Injection","id":"CVE-2026-35184"},"products":["HAXiam"],"published":"2026-04-06","related":[{"cvss_score":4.3,"headline":"HAXiam allows for User Enumeration","id":"CVE-2025-54129","kev_date_added":null,"published":"2025-07-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["haxtheweb"]},"summary":"Unauthenticated attackers can access the public /server-status endpoint to steal authentication tokens and monitor user activity in HAX CMS.","url":"https://insights.sbomify.com/CVE-2026-35185/"}