Persistent account access via uncleared sessioncode
Published Jul 22, 2026 · Updated Jul 22, 2026
Insufficient session expiration in Question2Answer 1.8.8 and earlier allows attackers to retain account access with an old persistent cookie. The qa_finish_reset_user() forgot-password handler leaves the account's sessioncode unchanged, so pre-reset qa_session cookies remain valid after the password reset. Exploitation requires a previously obtained persistent cookie and grants authenticated access as the affected account.
Summary
What happened
Insufficient session expiration in Question2Answer 1.8.8 and earlier allows attackers to retain account access with an old persistent cookie. The qa_finish_reset_user() forgot-password handler leaves the account's sessioncode unchanged, so pre-reset qa_session cookies remain valid after the password reset. Exploitation requires a previously obtained persistent cookie and grants authenticated access as the affected account.
The record
- CVE
- CVE-2026-64829
- Published
- Jul 22, 2026
- Updated
- Jul 22, 2026
- Vendor
- Question2Answer
- Product
- Question2Answer
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2026CVE publishedPublication date reported by the CVE source.
- Jul 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.8.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo