Account access persistence via unrevoked session tokens
Published Aug 5, 2026 · Updated Aug 5, 2026
Improper session invalidation in Flarum before 1.8.16 allows remote authenticated users to retain account access after password changes. TokensClearer handles PasswordChanged by deleting password_tokens rows but does not delete matching access_tokens rows. Exploitation requires an already valid victim token; retained session, remember, and developer tokens preserve the victim's privileges.
Summary
What happened
Improper session invalidation in Flarum before 1.8.16 allows remote authenticated users to retain account access after password changes. TokensClearer handles PasswordChanged by deleting password_tokens rows but does not delete matching access_tokens rows. Exploitation requires an already valid victim token; retained session, remember, and developer tokens preserve the victim's privileges.
The record
- CVE
- CVE-2026-39924
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Flarum
- Product
- Flarum
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.16
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.
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