CVE-2024-5386 json
Account Hijacking via Password Reset Token Leak in lunary-ai/lunary
published 2026-02-02 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-55392
- cvss
- 9.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
In lunary-ai/lunary version 1.2.2, an account hijacking vulnerability exists due to a password reset token leak. A user with a 'viewer' role can exploit this vulnerability to hijack another user's account by obtaining the password reset token. The vulnerability is triggered when the 'viewer' role user sends a specific request to the server, which responds with a password reset token in the 'recoveryToken' parameter. This token can then be used to reset the password of another user's account without authorization. The issue results from an excessive attack surface, allowing lower-privileged users to escalate their privileges and take over accounts.
Patch / fix
- lunary-ai lunary-ai/lunary 1.2.14
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 9 mo ago
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/602eb4a1-305d-46d6-b975-5a5d8b040ad1 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.6 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- lunary-ai lunary-ai/lunary
Classification
- Weakness
-
- CWE-1125 Excessive Attack Surface
References
-
github.com
/lunary-ai/lunary/commit/fc7ab3d5621c18992da5dab3a2a9a8d227d42311
broken-link
-
huntr.com
/bounties/602eb4a1-305d-46d6-b975-5a5d8b040ad1
exploit, patch, third-party-advisory
Sources
- CVE List CVE-2024-5386
- NVD CVE-2024-5386
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.