CVE-2023-49508 json
YetiForceCRM Directory Traversal vulnerability
published 2024-02-16 2 y ago modified 2026-06-17 4 mo ago also GHSA-394m-vxwj-363j , EUVD-2024-0780
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist yetiforce/yetiforce-crm 6.5.0
- yetiforce yetiforce_customer_relationship_management 6.5.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | yetiforce/yetiforce-crm | <6.5.0 |
6.5.0 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/YetiForceCompany/YetiForceCRM/commit/ba3a348aa6ecdf0a1d8b289cbb679bebcda7a132
web, patch
-
huntr.com
/bounties/29ed641d-eb03-4532-aed4-f96e11f78983/
permissions-required
-
github.com
/c4v4r0n/Research/tree/main/CVE-2023-49508
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-49508
advisory
-
github.com
/YetiForceCompany/YetiForceCRM
package
-
huntr.com
/bounties/29ed641d-eb03-4532-aed4-f96e11f78983
web
Sources
- CVE List CVE-2023-49508
- GitHub Advisory GHSA-394m-vxwj-363j
- NVD CVE-2023-49508
Fencer Vulns 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.