Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist
Not in CISA KEV

GHSA-c39w-3pjx-qc7m leantime/leantime

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.

Leantime allows Stored Cross-Site Scripting (XSS)

Published
Feb 21, 2025
Updated
Feb 21, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Feb 21, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘leantime/leantime

Real-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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistleantime/leantimeall versions3.3composer require leantime/leantime:^3.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c39w-3pjx-qc7m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-c39w-3pjx-qc7m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.
O3 Security · Impact-Aware SCA

Is GHSA-c39w-3pjx-qc7m in your dependencies?

O3 Security finds GHSA-c39w-3pjx-qc7m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-c39w-3pjx-qc7m: leantime/leantime | O3 Security