How severe is GHSA-v4q9-437p-mhpg?

No CVSS score has been assigned to GHSA-v4q9-437p-mhpg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v4q9-437p-mhpg?

GHSA-v4q9-437p-mhpg affects the following packages: leantime/leantime (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-v4q9-437p-mhpg?

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

How do I detect GHSA-v4q9-437p-mhpg 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-v4q9-437p-mhpg 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-v4q9-437p-mhpg?

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

Is GHSA-v4q9-437p-mhpg actively exploited in the wild?

No public exploit code has been indexed for GHSA-v4q9-437p-mhpg 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-v4q9-437p-mhpg published, and has it been updated?

GHSA-v4q9-437p-mhpg was published on February 21, 2025 and was last updated on February 21, 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

GHSA-v4q9-437p-mhpg — leantime/leantime

GHSA-v4q9-437p-mhpg is a remote code execution vulnerability in leantime/leantime. A fix is available for leantime/leantime — see the affected versions and patch details below.

Leantime allows Cross Site Scripting (XSS) and SQL Injection (SQLi)

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

Summary

A cross-site scripting (XSS) vulnerability has been identified in Leantime. The vulnerability allows an attacker to inject malicious scripts into certain fields, potentially leading to the execution of arbitrary code or unauthorized access to user-sensitive information. The code does not include any validation or sanitization of the $_GET["id"] parameter. As a result, it directly incorporates the user-supplied value into the source path without any checks.

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-v4q9-437p-mhpg 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v4q9-437p-mhpg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-v4q9-437p-mhpg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A cross-site scripting (XSS) vulnerability has been identified in Leantime. The vulnerability allows an attacker to inject malicious scripts into certain fields, potentially leading to the execution of arbitrary code or unauthorized access to user-sensitive information. The code does not include any validation or sanitization of the $_GET["id"] parameter. As a result, it directly incorporates the user-supplied value into the source path without any checks.

O3 Security · Impact-Aware SCA

Is GHSA-v4q9-437p-mhpg in your dependencies?

O3 Security finds GHSA-v4q9-437p-mhpg across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works