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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

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.

How does O3 Security protect against GHSA-f679-254h-qhvj?

O3 pinpoints whether GHSA-f679-254h-qhvj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.

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

Blast Radius

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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.
How O3 protects you
O3 pinpoints whether GHSA-f679-254h-qhvj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f679-254h-qhvj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-f679-254h-qhvj across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-f679-254h-qhvj