What is GHSA-3HFJ-QCVJ-4HX8?

GHSA-3HFJ-QCVJ-4HX8 is a low-severity missing authorization vulnerability in leantime/leantime (composer), affecting versions < 3.3. It is fixed in 3.3. The application does not perform an authorization check before performing a sensitive operation.

Which versions of leantime/leantime are affected by GHSA-3HFJ-QCVJ-4HX8?

leantime/leantime (composer) versions < 3.3 is affected.

Is there a fix for GHSA-3HFJ-QCVJ-4HX8?

Yes. GHSA-3HFJ-QCVJ-4HX8 is fixed in 3.3. Upgrade to this version or later.

Is GHSA-3HFJ-QCVJ-4HX8 exploitable, and should I be worried?

Whether GHSA-3HFJ-QCVJ-4HX8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-3HFJ-QCVJ-4HX8 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-3HFJ-QCVJ-4HX8 in leantime/leantime

Q: Which versions of leantime/leantime are affected by GHSA-3HFJ-QCVJ-4HX8?

leantime/leantime (composer) versions < 3.3 is affected.

Q: Is there a fix for GHSA-3HFJ-QCVJ-4HX8?

Yes. GHSA-3HFJ-QCVJ-4HX8 is fixed in 3.3. Upgrade to this version or later.

Q: Is GHSA-3HFJ-QCVJ-4HX8 exploitable, and should I be worried?

Whether GHSA-3HFJ-QCVJ-4HX8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-3HFJ-QCVJ-4HX8 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-3HFJ-QCVJ-4HX8?

Upgrade leantime/leantime to 3.3 or later.

Summary

Leantime has Missing Authorization Check for Host Parameter

Finding Description

Application has functionality for a user to view profile information. It does not have an implemented authorization check for "Host" parameter which allows a user to view profile information of another user by replacing "Host" parameter.

Impact

By exploiting this vulnerability an attacker can able to view profile information (but not anything else or change anything)

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

leantime/leantime (< 3.3)

Security releases

leantime/leantime → 3.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade leantime/leantime to 3.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-3HFJ-QCVJ-4HX8? GHSA-3HFJ-QCVJ-4HX8 is a low-severity missing authorization vulnerability in leantime/leantime (composer), affecting versions < 3.3. It is fixed in 3.3. The application does not perform an authorization check before performing a sensitive operation.
Which versions of leantime/leantime are affected by GHSA-3HFJ-QCVJ-4HX8? leantime/leantime (composer) versions < 3.3 is affected.
Is there a fix for GHSA-3HFJ-QCVJ-4HX8? Yes. GHSA-3HFJ-QCVJ-4HX8 is fixed in 3.3. Upgrade to this version or later.
Is GHSA-3HFJ-QCVJ-4HX8 exploitable, and should I be worried? Whether GHSA-3HFJ-QCVJ-4HX8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-3HFJ-QCVJ-4HX8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-3HFJ-QCVJ-4HX8? Upgrade leantime/leantime to 3.3 or later.

Other vulnerabilities in leantime/leantime

CVE-IDSeverityPackage summary

GHSA-QRFH-CC86-VC8CMediumleantime/leantime: Leantime has HTML injection through firstname and lastname fields GHSA-F679-254H-QHVJLowleantime/leantime: Leantime allows Cross-Site Scripting (XSS)CVE-2025-28254Mediumleantime/leantime: Leantime affected by Improper Neutralization of HTML Tags GHSA-C39W-3PJX-QC7MHighleantime/leantime: Leantime allows Stored Cross-Site Scripting (XSS)GHSA-92XH-6X7V-4RMQMediumleantime/leantime: Leantime allows Cross-Site Request Forgery (CSRF)