Account takeover via reusable password reset tokens
Published Feb 27, 2026 · Updated Feb 27, 2026
Business logic errors in Vikunja before 2.1.0 allow attackers with a password reset token to take over the associated account. ResetPassword deletes TokenEmailConfirm instead of TokenPasswordReset, while the cleanup cron selects tokens newer than 24 hours and leaves older reset tokens stored. Possession of one intercepted token allows repeated password resets and persistent account takeover even after the victim changes the password.
Summary
What happened
Business logic errors in Vikunja before 2.1.0 allow attackers with a password reset token to take over the associated account. ResetPassword deletes TokenEmailConfirm instead of TokenPasswordReset, while the cleanup cron selects tokens newer than 24 hours and leaves older reset tokens stored. Possession of one intercepted token allows repeated password resets and persistent account takeover even after the victim changes the password.
The record
- CVE
- CVE-2026-28268
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- Vikunja
- Product
- Vikunja
- Classifications
- CWE-459, CWE-640, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2026CVE publishedPublication date reported by the CVE source.
- Feb 27, 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=< 2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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