Leantime 3.6.2 contains a cross-site request forgery vulnerability that allows unauthenticated attackers to perform state-changing actions on behalf… (CVE-2026-66416)
Leantime version 3.6.2 has a cross-site request forgery (CSRF) vulnerability due to the exclusion of the Laravel VerifyCsrfToken middleware from the global middleware stack. This flaw allows unauthenticated attackers to perform state-changing actions on behalf of authenticated users by tricking them into submitting malicious requests. Such actions include creating or deleting projects, modifying settings, and changing permissions. There is no information about a patch or fix currently available.
AI Analysis
Technical Summary
Leantime 3.6.2 is vulnerable to CSRF attacks because the Laravel VerifyCsrfToken middleware is excluded from the global middleware stack in app/Http/Kernel.php. This omission enables attackers to craft malicious web pages that, when visited by authenticated users, can trigger unauthorized POST, PUT, and DELETE requests. These requests can alter application state by creating or deleting projects, changing settings, or modifying permissions without the users' consent or knowledge. The vulnerability is identified as CWE-352 and has a high severity rating. No patch or official remediation has been documented in the provided data.
Potential Impact
An attacker can exploit this vulnerability to perform unauthorized state-changing operations on behalf of authenticated users without their consent. This can lead to unauthorized project creation or deletion, alteration of application settings, and changes to user permissions, potentially compromising the integrity and security of the affected Leantime instance.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider implementing additional CSRF protections manually or restrict access to trusted users only. Monitoring for suspicious activity related to state-changing requests is advisable. Avoid interacting with untrusted links or websites that could trigger CSRF attacks.
Leantime 3.6.2 contains a cross-site request forgery vulnerability that allows unauthenticated attackers to perform state-changing actions on behalf… (CVE-2026-66416)
Description
Leantime version 3.6.2 has a cross-site request forgery (CSRF) vulnerability due to the exclusion of the Laravel VerifyCsrfToken middleware from the global middleware stack. This flaw allows unauthenticated attackers to perform state-changing actions on behalf of authenticated users by tricking them into submitting malicious requests. Such actions include creating or deleting projects, modifying settings, and changing permissions. There is no information about a patch or fix currently available.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Leantime 3.6.2 is vulnerable to CSRF attacks because the Laravel VerifyCsrfToken middleware is excluded from the global middleware stack in app/Http/Kernel.php. This omission enables attackers to craft malicious web pages that, when visited by authenticated users, can trigger unauthorized POST, PUT, and DELETE requests. These requests can alter application state by creating or deleting projects, changing settings, or modifying permissions without the users' consent or knowledge. The vulnerability is identified as CWE-352 and has a high severity rating. No patch or official remediation has been documented in the provided data.
Potential Impact
An attacker can exploit this vulnerability to perform unauthorized state-changing operations on behalf of authenticated users without their consent. This can lead to unauthorized project creation or deletion, alteration of application settings, and changes to user permissions, potentially compromising the integrity and security of the affected Leantime instance.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider implementing additional CSRF protections manually or restrict access to trusted users only. Monitoring for suspicious activity related to state-changing requests is advisable. Avoid interacting with untrusted links or websites that could trigger CSRF attacks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w22w-fm87-f6gx
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-66416"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a6bdd899c2644c7f8da711e
Added to database: 07/30/2026, 23:26:01 UTC
Last enriched: 07/30/2026, 23:32:00 UTC
Last updated: 07/31/2026, 02:00:41 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.