Leantime has HTML injection through firstname and lastname fields

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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) 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: <h1INJECTED</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(): 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

Published by the source

5 Mar 2026, 18:05 UTC

Last modified by the source

5 Mar 2026, 18:05 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qrfh-cc86-vc8c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-qrfh-cc86-vc8c

Advisory: Leantime has HTML injection through firstname and lastname fields
IDs: GHSA-qrfh-cc86-vc8c
Record: https://patchnext.com/advisories/ghsa-qrfh-cc86-vc8c (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: leantime/leantime 3.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist leantime/leantime: affected < 3.3.0; fixed in 3.3.0

## Suggested inspection (read-only)
- Packagist leantime/leantime: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on leantime/leantime.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qrfh-cc86-vc8c (GitHub-reviewed advisory GHSA-qrfh-cc86-vc8c lists affected ranges: Packagist leantime/leantime >=0 <3.3.0)

Commands are suggestions: review each one before running it.