GHSA-QRFH-CC86-VC8C

Leantime v2.3.27 is vulnerable to Stored HTML Injection. The firstname and lastname fields in the admin user edit page are rendered without HTML escaping, allowing an authenticated user to inject arbitrary HTML that executes when the profile is viewed.

Vulnerable File

app/Domain/Users/Templates/editUser.tpl.php

Vulnerable Code (Lines ~14-17)

value="<?php echo $values['firstname'] ?>"
value="<?php echo $values['lastname'] ?>"

These fields output raw user input without sanitization.

Steps to Reproduce

1. Login as admin > Go to Settings > Users > Edit any user
2. Enter HTML payload in First Name or Last Name field:
   <h1>INJECTED</h1>
3. Save the user profile
4. Create or view an article, the injected HTML renders in the author name

• Stored HTML injection visible to all users viewing affected content
• Can be used for phishing, fake login forms, and UI defacement
• Affects all versions before 3.3.0

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

GHSA-QRFH-CC86-VC8C has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

Replace unescaped echo with htmlspecialchars():

value="<?php echo htmlspecialchars($values['firstname'], ENT_QUOTES, 'UTF-8') ?>"
value="<?php echo htmlspecialchars($values['lastname'], ENT_QUOTES, 'UTF-8') ?>"

Or use the existing $this->e() helper already used in editOwn.tpl.php.

1. What is GHSA-QRFH-CC86-VC8C? GHSA-QRFH-CC86-VC8C is a medium-severity cross-site scripting (XSS) vulnerability in leantime/leantime (composer), affecting versions < 3.3.0. It is fixed in 3.3.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is GHSA-QRFH-CC86-VC8C? GHSA-QRFH-CC86-VC8C has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of leantime/leantime are affected by GHSA-QRFH-CC86-VC8C? leantime/leantime (composer) versions < 3.3.0 is affected.
4. Is there a fix for GHSA-QRFH-CC86-VC8C? Yes. GHSA-QRFH-CC86-VC8C is fixed in 3.3.0. Upgrade to this version or later.
5. Is GHSA-QRFH-CC86-VC8C exploitable, and should I be worried? Whether GHSA-QRFH-CC86-VC8C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-QRFH-CC86-VC8C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-QRFH-CC86-VC8C? Upgrade leantime/leantime to 3.3.0 or later.