{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64829 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-64829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-64829 is a critical authentication bypass vulnerability in q2a question2answer, published on 22 Jul 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-64829 and fix it if it is affected.\n\nWhat it is: CVE-2026-64829 is a critical authentication bypass vulnerability in q2a question2answer, published on 22 Jul 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-64829 in the wild and no public exploit code.\n\nAffected product: q2a question2answer. 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-64829/ (Markdown: https://insights.sbomify.com/CVE-2026-64829/index.md)","id":"CVE-2026-64829","markdown":"https://insights.sbomify.com/CVE-2026-64829/index.md","name":"CVE-2026-64829","record":{"aliases":["GHSA-88rm-6cpc-9j4w"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Q2A web application","requires_auth":"none","summary":"Attackers with a valid remember-me cookie can retain access after a password reset because the forgot-password flow fails to invalidate the session code.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Question2Answer through 1.8.8 contains a session invalidation vulnerability that allows attackers with a previously obtained remember-me cookie to retain authenticated access by exploiting the forgot-password reset flow's failure to clear the sessioncode field in qa-include/app/users-edit.php. While the normal password-change flow in qa-include/pages/account.php explicitly clears the sessioncode to invalidate persistent qa_session cookies, the forgot-password handler qa_finish_reset_user() omits this step, allowing any valid persistent cookie issued before the reset to continue authenticating the account after the password reset completes.","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":"Question2Answer 1.8.8 Session Fixation via Forgot-Password Flow","id":"CVE-2026-64829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"FFmpeg 2.1 - 8.1.2 Heap Buffer Overflow via VobSub Subtitle Demuxer","id":"CVE-2026-64830"},"packages":[],"prev":{"headline":"Froiden TableTrack 1.3.10 Stored XSS via Order Notes Field","id":"CVE-2026-64828"},"products":["question2answer"],"published":"2026-07-22","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["q2a"]},"summary":"Attackers with a valid remember-me cookie can retain access after a password reset because the forgot-password flow fails to invalidate the session code.","url":"https://insights.sbomify.com/CVE-2026-64829/"}