Account takeover via unchecked expired reset tokens
Published Aug 5, 2026 · Updated Aug 5, 2026
Password-reset expiry bypass in Flarum before 1.8.16 allows remote attackers with stale tokens to take over affected accounts. SavePasswordController::handle() passes the supplied passwordToken to PasswordToken::findOrFail(), which checks only database presence and omits the 24-hour expiry enforced by GET /reset/{token}. Possession of an expired token from a leaked email or database backup is required; POST /reset then changes the account password and issues an authenticated session.
Summary
What happened
Password-reset expiry bypass in Flarum before 1.8.16 allows remote attackers with stale tokens to take over affected accounts. SavePasswordController::handle() passes the supplied passwordToken to PasswordToken::findOrFail(), which checks only database presence and omits the 24-hour expiry enforced by GET /reset/{token}. Possession of an expired token from a leaked email or database backup is required; POST /reset then changes the account password and issues an authenticated session.
The record
- CVE
- CVE-2026-39923
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Flarum
- Product
- Flarum
- Classifications
- CWE-324, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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.
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