{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-53642 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53642 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53642 is a medium-severity vulnerability in haxtheweb issues, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53642 and fix it if it is affected.\n\nWhat it is: CVE-2025-53642 is a medium-severity vulnerability in haxtheweb issues, published on 11 Jul 2025. 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-2025-53642 in the wild and no public exploit code.\n\nAffected product: haxtheweb issues. 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-2025-53642/ (Markdown: https://insights.sbomify.com/CVE-2025-53642/index.md)","id":"CVE-2025-53642","markdown":"https://insights.sbomify.com/CVE-2025-53642/index.md","name":"CVE-2025-53642","record":{"aliases":["GHSA-g4f5-5w5j-p5jg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"HAXcms backend","requires_auth":"none","summary":"Attackers can maintain access after logout because sessions are not terminated and cookies are not cleared, allowing potential account takeover.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"haxcms-nodejs","vendor":"psu"},{"product":"haxcms-php","vendor":"psu"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"haxcms-nodejs and haxcms-php are backends for HAXcms. The logout function within the application does not terminate a user's session or clear their cookies. Additionally, the application issues a refresh token when logging out. This vulnerability is fixed in 11.0.6.","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":"haxcms-nodejs and haxcms-php Improperly Terminate Sessions","id":"CVE-2025-53642","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"AIOHTTP is vulnerable to HTTP Request/Response Smuggling through incorrect parsing of chunked trailer sections","id":"CVE-2025-53643"},"packages":[],"prev":{"headline":"Postiz allows header mutation in middleware facilitates resulting in SSRF","id":"CVE-2025-53641"},"products":["issues"],"published":"2025-07-11","related":[{"cvss_score":9.3,"headline":"HAXcms's Insecure Default Configuration Leads to Unauthenticated Access","id":"CVE-2025-54127","kev_date_added":null,"published":"2025-07-21"},{"cvss_score":8.6,"headline":"HaxCMS-PHP Command Injection Vulnerability","id":"CVE-2025-49141","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.5,"headline":"Hax CMS Stored Cross-Site Scripting vulnerability","id":"CVE-2025-49137","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.3,"headline":"HAX CMS Backend Lacks Comprehensive Authorization Checks","id":"CVE-2025-54378","kev_date_added":null,"published":"2025-07-26"},{"cvss_score":8.1,"headline":"HAXcms Has Stored XSS Vulnerability that May Lead to Account Takeover","id":"CVE-2026-22704","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":7.3,"headline":"NodeJS version of the HAX CMS application is distributed with Default Secrets","id":"CVE-2025-54137","kev_date_added":null,"published":"2025-07-22"},{"cvss_score":7.2,"headline":"HAX CMS NodeJs's Disabled Content Security Policy Enables Cross-Site Scripting","id":"CVE-2025-54128","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-14","vendors":["haxtheweb"]},"summary":"Attackers can maintain access after logout because sessions are not terminated and cookies are not cleared, allowing potential account takeover.","url":"https://insights.sbomify.com/CVE-2025-53642/"}