CVE-2026-64829: Insufficient Session Expiration in q2a question2answer
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.
AI Analysis
Technical Summary
CVE-2026-64829 describes a vulnerability in Question2Answer (q2a) up to version 1.8.8 where the forgot-password reset process does not clear the sessioncode field in qa-include/app/users-edit.php. This omission allows an attacker who has a valid persistent remember-me cookie issued before the password reset to continue authenticating as the user even after the password has been reset. The normal password-change flow in qa-include/pages/account.php explicitly clears the sessioncode to invalidate persistent qa_session cookies, but the forgot-password handler qa_finish_reset_user() lacks this step, resulting in insufficient session expiration and potential unauthorized access.
Potential Impact
An attacker with a previously obtained remember-me cookie can maintain authenticated access to a user account even after the user resets their password via the forgot-password flow. This undermines the security of the password reset process by allowing session persistence beyond intended expiration, potentially leading to unauthorized account access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider invalidating all persistent sessions manually after password resets or disabling the remember-me functionality as a temporary mitigation.
CVE-2026-64829: Insufficient Session Expiration in q2a question2answer
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.
CVSS v4.0
Score 9.1critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-64829 describes a vulnerability in Question2Answer (q2a) up to version 1.8.8 where the forgot-password reset process does not clear the sessioncode field in qa-include/app/users-edit.php. This omission allows an attacker who has a valid persistent remember-me cookie issued before the password reset to continue authenticating as the user even after the password has been reset. The normal password-change flow in qa-include/pages/account.php explicitly clears the sessioncode to invalidate persistent qa_session cookies, but the forgot-password handler qa_finish_reset_user() lacks this step, resulting in insufficient session expiration and potential unauthorized access.
Potential Impact
An attacker with a previously obtained remember-me cookie can maintain authenticated access to a user account even after the user resets their password via the forgot-password flow. This undermines the security of the password reset process by allowing session persistence beyond intended expiration, potentially leading to unauthorized account access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider invalidating all persistent sessions manually after password resets or disabling the remember-me functionality as a temporary mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-20T18:27:48.161Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6123219c2644c7f89b2d40
Added to database: 07/22/2026, 20:08:01 UTC
Last enriched: 07/22/2026, 20:22:05 UTC
Last updated: 07/23/2026, 01:35:19 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.