Skip to content
Fencer Intel
medium 5.4

GHSA-qrfh-cc86-vc8c json

Leantime has HTML injection through firstname and lastname fields

published 8mo ago modified 8mo ago

cvss
5.4
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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) ```php 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

### Fix Replace unescaped `echo` with `htmlspecialchars()`: ```php 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

Patch / fix

  • packagist leantime/leantime 3.3.0

Is GHSA-qrfh-cc86-vc8c in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist leantime/leantime
<3.3.0
3.3.0

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.