YetiForceCRM Directory Traversal vulnerabilityGHSA-394m-vxwj-363j
MEDIUMFix: YetiForceCompany/YetiForceCRM@ba3a348GHSA-394m-vxwj-363j is a medium-severity (CVSS 6.5) Path Traversal vulnerability in yetiforce/yetiforce-crm. A fix is available for yetiforce/yetiforce-crm — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-394m-vxwj-363j.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
yetiforce/yetiforce-crmReal-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
Directory Traversal vulnerability in YetiForceCompany YetiForceCRM versions 6.4.0 and before allows a remote authenticated attacker to obtain sensitive information via the license parameter in the LibraryLicense.php component.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | yetiforce/yetiforce-crm | all versions | 6.5.0composer require yetiforce/yetiforce-crm:^6.5.0 |
Affected Products
yetiforce customer relationship managementyetiforceDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yetiforce/yetiforce-crm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update yetiforce/yetiforce-crm to 6.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-394m-vxwj-363j is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-394m-vxwj-363j in your dependencies?
Find it across Packagist, including transitive dependencies.