CVE-2024-27474: leantime · n/a
Affects leantimeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubleantime/leantimepkg:github/leantime/leantimeOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-27474, organizations should implement the following specific measures: 1) Apply any official patches or updates from Leantime as soon as they become available. 2) If patches are not yet available, implement manual CSRF protections such as adding anti-CSRF tokens to all state-changing requests, especially those accessible to administrators. 3) Enforce strict session management, including validating the origin and referrer headers for sensitive requests. 4) Limit administrative interface access to trusted IP ranges or VPNs to reduce exposure. 5) Educate users, particularly administrators, about phishing and social engineering risks to minimize the chance of user interaction with malicious content. 6) Monitor logs for unusual administrative actions or requests originating from unexpected sources. 7) Consider implementing multi-factor authentication (MFA) to add an additional layer of security for administrative accounts. 8) Regularly review and audit user permissions to ensure least privilege principles are enforced. These targeted actions go beyond generic advice by focusing on immediate risk reduction in the absence of official patches.
Description
Leantime 3.0.6 is vulnerable to Cross Site Request Forgery (CSRF). This vulnerability allows malicious actors to perform unauthorized actions on behalf of authenticated users, specifically administrators.