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 affects Question2Answer through version 1.8.8. The vulnerability arises because the forgot-password reset flow (handled in qa_finish_reset_user() within qa-include/app/users-edit.php) fails to clear the sessioncode field. This omission means that any valid persistent qa_session cookie issued before the password reset remains valid, allowing attackers who have previously obtained a remember-me cookie to retain authenticated access after the password reset completes. In contrast, the normal password-change flow explicitly clears the sessioncode to invalidate persistent sessions. This discrepancy leads to insufficient session expiration and persistent authentication despite password resets.
Potential Impact
Attackers with a previously obtained remember-me cookie can bypass session invalidation during the forgot-password reset process, maintaining authenticated access to the affected account even after the password has been reset. This undermines the security of the password reset mechanism and can lead to unauthorized account access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider invalidating all active sessions manually after password resets and monitor for updates from the vendor regarding an official fix.
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 affects Question2Answer through version 1.8.8. The vulnerability arises because the forgot-password reset flow (handled in qa_finish_reset_user() within qa-include/app/users-edit.php) fails to clear the sessioncode field. This omission means that any valid persistent qa_session cookie issued before the password reset remains valid, allowing attackers who have previously obtained a remember-me cookie to retain authenticated access after the password reset completes. In contrast, the normal password-change flow explicitly clears the sessioncode to invalidate persistent sessions. This discrepancy leads to insufficient session expiration and persistent authentication despite password resets.
Potential Impact
Attackers with a previously obtained remember-me cookie can bypass session invalidation during the forgot-password reset process, maintaining authenticated access to the affected account even after the password has been reset. This undermines the security of the password reset mechanism and can lead to unauthorized account access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider invalidating all active sessions manually after password resets and monitor for updates from the vendor regarding an official fix.
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: 08/07/2026, 13:01:35 UTC
Last updated: 09/03/2026, 22:52:13 UTC
Views: 72
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.