GHSA-qrfh-cc86-vc8c
Leantime has HTML injection through firstname and lastname fields
Summary
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
- Login as admin > Go to Settings > Users > Edit any user
- Enter HTML payload in First Name or Last Name field:
<h1>INJECTED</h1> - Save the user profile
- Create or view an article — the injected HTML renders in the author name
Fix
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.
Impact
- 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
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- Required
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
What each source reports
GitHub Advisories Score used
Leantime has HTML injection through firstname and lastname fields
Summary
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
- Login as admin > Go to Settings > Users > Edit any user
- Enter HTML payload in First Name or Last Name field:
<h1>INJECTED</h1> - Save the user profile
- Create or view an article — the injected HTML renders in the author name
Fix
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.
Impact
- 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
- Record
GHSA-qrfh-cc86-vc8c- CVSS 3.1
- 5.4 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N - Weakness
- CWE-79
- Updated
- 2026-11-02
OSV
Leantime has HTML injection through firstname and lastname fields
Summary
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
- Login as admin > Go to Settings > Users > Edit any user
- Enter HTML payload in First Name or Last Name field:
<h1>INJECTED</h1> - Save the user profile
- Create or view an article — the injected HTML renders in the author name
Fix
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.
Impact
- 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
- Record
GHSA-qrfh-cc86-vc8c- CVSS 3.1
- 5.4 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N - Weakness
- CWE-79
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
leantime/leantimePackagist |
before 3.3.0 | 3.3.0 |
leantime/leantimePackagist |
before 3.3.0, plus listed versions 2.42.4-beta2.4-beta-72.4-beta-82.4.1 Show 45 moreShow less2.4.22.4.32.4.42.4.52.4.72.4.83.0.03.0.0-beta3.0.13.0.23.0.33.0.43.0.53.0.63.0.73.1.0-beta3.1.13.1.23.1.33.1.43.2.03.2.0-beta3.2.0-beta-23.2.13.3v2.0v2.0.1v2.0.10v2.0.11v2.0.12v2.0.13v2.0.14v2.0.15v2.0.2v2.0.3v2.0.4v2.0.5v2.0.6v2.0.7v2.0.8v2.0.9v2.1v2.1-betav2.1-beta2v2.1-beta3 |
3.3.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-qrfh-cc86-vc8c is a medium vulnerability (CVSS 5.4) in leantime/leantime, published March 5, 2026. No source lists public exploit code. Fixed in leantime/leantime 3.3.0.
References
Left out here: 51 versions. The JSON record has them.