How severe is GHSA-f679-254h-qhvj?

No CVSS score has been assigned to GHSA-f679-254h-qhvj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f679-254h-qhvj?

GHSA-f679-254h-qhvj affects the following packages: leantime/leantime (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-f679-254h-qhvj?

Update leantime/leantime to 3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f679-254h-qhvj is resolved across your whole dependency graph.

How do I detect GHSA-f679-254h-qhvj in my Packagist dependencies?

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.

How do I mitigate GHSA-f679-254h-qhvj if there is no patch (or I can't update yet)?

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.

Is GHSA-f679-254h-qhvj actively exploited in the wild?

No public exploit code has been indexed for GHSA-f679-254h-qhvj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-f679-254h-qhvj published, and has it been updated?

GHSA-f679-254h-qhvj was published on February 21, 2025 and was last updated on February 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Leantime allows Cross-Site Scripting (XSS)GHSA-f679-254h-qhvj

GHSA-f679-254h-qhvj is a security vulnerability in leantime/leantime. A fix is available for leantime/leantime — see the affected versions and patch details below.

Published

Feb 21, 2025

Updated

Feb 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 22, 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

Summary

There is a cross-site scripting vulnerability on To-Do that affects a title field of a To-Do.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`leantime/leantime`	all versions	3.3`composer require leantime/leantime:^3.3`

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update leantime/leantime to 3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f679-254h-qhvj 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

### Summary There is a cross-site scripting vulnerability on To-Do that affects a title field of a To-Do.

O3 Security · Impact-Aware SCA

Is GHSA-f679-254h-qhvj in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works