Leantime has Insufficiently Protected Credentials

published 2025-02-21 last yr. modified 2025-02-21 last yr.

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Due to improper cache control an attacker can view sensitive information even if they are not logged into the account anymore.

Additional Information:

1.The issue was identified during routine security testing. 2.This vulnerability poses a significant risk to user privacy and data security. 3.Urgent action is recommended to mitigate this vulnerability and protect user data from unauthorized access.

Patch / fix

fixed in 1

packagist leantime/leantime 3.3

Is GHSA-h6w8-27ph-c385 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
packagist	leantime/leantime	<3.3	3.3

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

References

Sources

GitHub Advisory GHSA-h6w8-27ph-c385

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.