GHSA-m492-gv72-xvxj: Kimai Password Reset Link Remains Valid After Password Change
Summary The LoginLink signature used for password reset URLs covers only the user's id — it does not include the password hash. After a user clicks a reset link and successfully changes their password, the same link remains valid for up to 2 additional uses within a 1-hour window. Anyone who intercepts or caches the original link can log in as the user even after the password has been changed.
Published Jul 1, 2026
Affected packages
kimai/kimai
- Ecosystem
- Composer (PHP)
- Affected
- <= 2.57.0
- Fixed in
- 2.58.0
- Check
composer show kimai/kimai
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The LoginLink signature used for password reset URLs covers only the user's id — it does not include the password hash. After a user clicks a reset link and successfully changes their password, the same link remains valid for up to 2 additional uses within a 1-hour window. Anyone who intercepts or caches the original link can log in as the user even after the password has been changed.
Details
config/packages/security.yaml:73-78 configures the login link:
login_link:
check_route: link_login_check
signature_properties: ['id']
lifetime: 900
max_uses: 3The HMAC signature covers only id, not password, username, or email. The effective lifetime for password reset links is extended to 3600 seconds by PasswordResetController.php:106-119 via getPasswordResetRetryLifetime().
After the first successful use (where the user sets a new password), the __pw_reset__ session flag is cleared by WizardController.php:105. Subsequent uses of the same link bypass the forced-password-reset wizard and grant a normal authenticated session.
Symfony's LoginLinkHandler::consumeLoginLink decrements a per-link counter but allows up to 3 total uses. Re-issuing a new link does not invalidate the old one.
The same vulnerability affects UserLoginLinkCommand.php:77, which generates admin-on-demand login links with the same signature scheme.
PoC
Step 1 — Generate a password reset link:
docker exec <kimai_container> bin/console kimai:user:login-link <username>Step 2 — Use the link to log in and change the password.
Step 3 — Open the same link in a different browser or incognito session.
The link logs the attacker in as a fully authenticated user, despite the password having been changed in Step 2.
Step 4 — The link works a third time (3 total uses within 1 hour).
Impact
A password reset link that leaks through any of the following channels remains a valid authentication credential even after the legitimate user has changed their password: corporate mail-relay scanners that pre-click links (Microsoft Defender ATP, Mimecast, Barracuda), shared inboxes, browser history sync across devices, HTTP referrer headers, or proxy/WAF logs. The user believes they have secured their account by setting a new password, but the leaked link still grants full access for up to 2 additional uses within the hour.
Solution
Login links now also use the password hash for generating the signature, which will immediately expire the link after the user changed the password.
Read for more information.
Credited to AzureADTrent.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-52821
Kimai: Improper Authorization Through Activity Creation with Preset Project Allows Creation Under Unauthorized Projects
medium5.3Jul 14, 2026CVE-2026-52822
Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation
medium5.3Jul 14, 2026CVE-2026-52823
Kimai: Login CSRF in the Timesheet Stop and Restart API Endpoints Allows Unauthorized State Changes
medium5.3Jul 14, 2026CVE-2026-52824
Kimai: Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover
critical9.1Jul 14, 2026CVE-2026-52825
Kimai has Improper Authorization in Team Member and Team Activity Assignment APIs Which Allows Expansion of Team Scope Beyond Authorized Visibility
medium5.3Jul 14, 2026CVE-2026-52826
Kimai: Improper Authorization in Project, Customer, and Activity Rate Edit Endpoints Allows Cross-Scope Rate Manipulation
medium5.3Jul 14, 2026
