CVE-2024-27477: n/a
In Leantime 3.0.6, a Cross-Site Scripting vulnerability exists within the ticket creation and modification functionality, allowing attackers to inject malicious JavaScript code into the title field of tickets (also known as to-dos). This stored XSS vulnerability can be exploited to perform Server-Side Request Forgery (SSRF) attacks.
AI Analysis
Technical Summary
CVE-2024-27477 identifies a stored Cross-Site Scripting (XSS) vulnerability in Leantime version 3.0.6, specifically within the ticket (to-do) creation and modification functionality. The vulnerability arises because the application fails to properly sanitize or encode user-supplied input in the ticket title field, allowing attackers to inject malicious JavaScript code that is stored persistently in the system. When other users or administrators view the affected tickets, the malicious script executes in their browsers, potentially stealing session tokens, performing actions on behalf of the user, or manipulating the interface. Uniquely, this XSS can be chained to perform Server-Side Request Forgery (SSRF) attacks, where the injected script causes the server to make unauthorized HTTP requests to internal or external resources, potentially exposing sensitive internal services or data. The vulnerability is remotely exploitable over the network without requiring authentication but does require user interaction (viewing the malicious ticket). The CVSS 3.1 base score is 6.1, reflecting medium severity with low attack complexity and no privileges required. No patches or official fixes have been released at the time of publication, and no known exploits are reported in the wild. The underlying weakness corresponds to CWE-79 (Improper Neutralization of Input During Web Page Generation).
Potential Impact
This vulnerability can lead to unauthorized execution of malicious scripts in the context of users’ browsers, compromising confidentiality and integrity of user sessions and data. The SSRF capability extends the impact by enabling attackers to pivot from the client-side to the server-side, potentially accessing internal services, bypassing firewalls, or exfiltrating sensitive information. For organizations, this could mean exposure of internal network resources, unauthorized data access, and potential lateral movement within the infrastructure. The medium CVSS score indicates a moderate risk, but the chained SSRF attack increases the threat surface. Public-facing Leantime installations used for project and task management are particularly at risk, as attackers can target users with crafted tickets. The absence of patches increases the window of exposure. While no active exploitation is reported, the vulnerability could be weaponized by attackers targeting organizations relying on Leantime for collaboration, especially those with sensitive internal networks accessible from the server.
Mitigation Recommendations
Organizations should immediately review and restrict input validation on the ticket title field to disallow or properly encode HTML and JavaScript content. Implement strict Content Security Policy (CSP) headers to reduce the impact of any injected scripts. Monitor logs for unusual ticket creation or modification activity that includes suspicious script tags or payloads. If possible, restrict access to the ticketing system to trusted users and networks until a patch is available. Employ web application firewalls (WAFs) with rules targeting XSS payloads and SSRF patterns. Educate users to avoid clicking on suspicious ticket links or content. Developers should prioritize releasing a patch that sanitizes and encodes user inputs correctly and validates server-side requests to prevent SSRF. Additionally, network segmentation and limiting server outbound requests can reduce SSRF impact. Regularly update and audit the Leantime installation and dependencies for security fixes.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, Netherlands, France, India, Brazil, Japan
CVE-2024-27477: n/a
Description
In Leantime 3.0.6, a Cross-Site Scripting vulnerability exists within the ticket creation and modification functionality, allowing attackers to inject malicious JavaScript code into the title field of tickets (also known as to-dos). This stored XSS vulnerability can be exploited to perform Server-Side Request Forgery (SSRF) attacks.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-27477 identifies a stored Cross-Site Scripting (XSS) vulnerability in Leantime version 3.0.6, specifically within the ticket (to-do) creation and modification functionality. The vulnerability arises because the application fails to properly sanitize or encode user-supplied input in the ticket title field, allowing attackers to inject malicious JavaScript code that is stored persistently in the system. When other users or administrators view the affected tickets, the malicious script executes in their browsers, potentially stealing session tokens, performing actions on behalf of the user, or manipulating the interface. Uniquely, this XSS can be chained to perform Server-Side Request Forgery (SSRF) attacks, where the injected script causes the server to make unauthorized HTTP requests to internal or external resources, potentially exposing sensitive internal services or data. The vulnerability is remotely exploitable over the network without requiring authentication but does require user interaction (viewing the malicious ticket). The CVSS 3.1 base score is 6.1, reflecting medium severity with low attack complexity and no privileges required. No patches or official fixes have been released at the time of publication, and no known exploits are reported in the wild. The underlying weakness corresponds to CWE-79 (Improper Neutralization of Input During Web Page Generation).
Potential Impact
This vulnerability can lead to unauthorized execution of malicious scripts in the context of users’ browsers, compromising confidentiality and integrity of user sessions and data. The SSRF capability extends the impact by enabling attackers to pivot from the client-side to the server-side, potentially accessing internal services, bypassing firewalls, or exfiltrating sensitive information. For organizations, this could mean exposure of internal network resources, unauthorized data access, and potential lateral movement within the infrastructure. The medium CVSS score indicates a moderate risk, but the chained SSRF attack increases the threat surface. Public-facing Leantime installations used for project and task management are particularly at risk, as attackers can target users with crafted tickets. The absence of patches increases the window of exposure. While no active exploitation is reported, the vulnerability could be weaponized by attackers targeting organizations relying on Leantime for collaboration, especially those with sensitive internal networks accessible from the server.
Mitigation Recommendations
Organizations should immediately review and restrict input validation on the ticket title field to disallow or properly encode HTML and JavaScript content. Implement strict Content Security Policy (CSP) headers to reduce the impact of any injected scripts. Monitor logs for unusual ticket creation or modification activity that includes suspicious script tags or payloads. If possible, restrict access to the ticketing system to trusted users and networks until a patch is available. Employ web application firewalls (WAFs) with rules targeting XSS payloads and SSRF patterns. Educate users to avoid clicking on suspicious ticket links or content. Developers should prioritize releasing a patch that sanitizes and encodes user inputs correctly and validates server-side requests to prevent SSRF. Additionally, network segmentation and limiting server outbound requests can reduce SSRF impact. Regularly update and audit the Leantime installation and dependencies for security fixes.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- mitre
- Date Reserved
- 2024-02-26T00:00:00.000Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6d7db7ef31ef0b57a4d2
Added to database: 2/25/2026, 9:45:33 PM
Last enriched: 2/26/2026, 11:03:26 AM
Last updated: 4/12/2026, 3:34:40 PM
Views: 13
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.