CVE-2026-39924: Flarum < 1.8.16 Session Persistence via Improper Access Token Revocation
Flarum before 1.8.16 contains an improper session invalidation vulnerability that allows attackers who hold a valid session token to retain full account access after a victim changes their password, because the accesstokens table is never cleared on password change events. The TokensClearer::clearPasswordTokens() function only removes rows from the passwordtokens table while leaving all active session cookies and API bearer tokens intact, including long-lived RememberAccessToken entries, and administrator-forced password resets via the user update endpoint are equally ineffective at revoking attacker-held sessions.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
flarumto a version that resolves this vulnerability.Fixed in 1.8.16 - Compensating control
Because access_tokens are not cleared on password change, revoke any potentially exposed session cookies/API bearer tokens (including long-lived RememberAccessToken entries) for affected accounts after password changes.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39924?
The severity of CVE-2026-39924 is medium with a score of 6.8.
How do I fix CVE-2026-39924?
To fix CVE-2026-39924, upgrade to Flarum version 1.8.16 or later.
What does CVE-2026-39924 affect?
CVE-2026-39924 affects the Flarum platform versions prior to 1.8.16.
What type of vulnerability is CVE-2026-39924?
CVE-2026-39924 is an improper session invalidation vulnerability.
What is the impact of CVE-2026-39924?
CVE-2026-39924 allows attackers to retain access to a user's account even after the user changes their password.