How severe is GHSA-92xh-6x7v-4rmq?

No CVSS score has been assigned to GHSA-92xh-6x7v-4rmq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-92xh-6x7v-4rmq?

GHSA-92xh-6x7v-4rmq affects the following packages: leantime/leantime (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-92xh-6x7v-4rmq?

Update leantime/leantime to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92xh-6x7v-4rmq is resolved across your whole dependency graph.

How do I detect GHSA-92xh-6x7v-4rmq 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-92xh-6x7v-4rmq 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-92xh-6x7v-4rmq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-92xh-6x7v-4rmq can be triaged on real exposure rather than presence alone.

Is GHSA-92xh-6x7v-4rmq actively exploited in the wild?

No public exploit code has been indexed for GHSA-92xh-6x7v-4rmq 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-92xh-6x7v-4rmq published, and has it been updated?

GHSA-92xh-6x7v-4rmq 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-92xh-6x7v-4rmq — leantime/leantime

GHSA-92xh-6x7v-4rmq is a security vulnerability in leantime/leantime. A fix is available for leantime/leantime — see the affected versions and patch details below.

Leantime allows Cross-Site Request Forgery (CSRF)

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

CSRF

Summary

A cross-site request forgery vulnerability allows a remote actor to create an account with Owner privileges. By luring an Owner or Administrator into clicking a button on an attacker-controlled website, a request will be issued, generating an account with the attacker's information and role of their choosing.

Impact

While the likelihood of a successful exploit is low, the impact would be high as the attacker could then gain complete control over the victim's environment.

Affected Packages

1 total 1 fixed

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

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.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92xh-6x7v-4rmq 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-92xh-6x7v-4rmq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-92xh-6x7v-4rmq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**CSRF** ### Summary A cross-site request forgery vulnerability allows a remote actor to create an account with Owner privileges. By luring an Owner or Administrator into clicking a button on an attacker-controlled website, a request will be issued, generating an account with the attacker's information and role of their choosing. ### Impact While the likelihood of a successful exploit is low, the impact would be high as the attacker could then gain complete control over the victim's environment.

O3 Security · Impact-Aware SCA

Is GHSA-92xh-6x7v-4rmq in your dependencies?

O3 Security finds GHSA-92xh-6x7v-4rmq 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