Leantime allows Stored Cross-Site Scripting (XSS)GHSA-c39w-3pjx-qc7m
GHSA-c39w-3pjx-qc7m is a security vulnerability in leantime/leantime. A fix is available for leantime/leantime — see the affected versions and patch details below.
Real-World Exposure
leantime/leantimeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Description
Leantime allows stored cross-site scripting (XSS) in the API key name while generating the API key.
Impact
Any low privileged user like manager, or editor, can create an API key with XSS payload. When admin will visit the Company page, the XSS will automatically get triggerred leading to the unauthorized action performed from the ADMIN account. Like, removing any user, or adding someone else as high privilege, and many more.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | leantime/leantime | all versions | 3.3composer require leantime/leantime:^3.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for leantime/leantime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update leantime/leantime to 3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c39w-3pjx-qc7m is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-c39w-3pjx-qc7m in your dependencies?
Find it across Packagist, including transitive dependencies.