CVE-2024-55415 json
DevDojo Voyager vulnerable to path traversal
published 2025-01-30 21 mo ago modified 2026-06-17 4 mo ago also GHSA-j63m-2vr6-fv7m , EUVD-2025-0173
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 17.6%
- EPSS 17.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
DevDojo Voyager through 1.8.0 is vulnerable to path traversal at the /admin/compass.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
17.63% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template DevDojo Voyager <=1.8.0 - Arbitrary File Read nuclei detection template
- sonarsource.com https://www.sonarsource.com/blog/the-tainted-voyage-uncovering-voyagers-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | tcg/voyager | <=1.8.0 |
no fix listed |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
sonarsource.com
/blog/the-tainted-voyage-uncovering-voyagers-vulnerabilities/
exploit, third-party-advisory
-
github.com
/thedevdojo/voyager/blob/1.6/src/Http/Controllers/VoyagerCompassController.php#L44
web, product
-
github.com
/thedevdojo/voyager/blob/1.6/src/Http/Controllers/VoyagerCompassController.php#L213
web, product
-
nvd.nist.gov
/vuln/detail/CVE-2024-55415
advisory
-
github.com
/thedevdojo/voyager
package
-
sonarsource.com
/blog/the-tainted-voyage-uncovering-voyagers-vulnerabilities
web
Sources
- CVE List CVE-2024-55415
- GitHub Advisory GHSA-j63m-2vr6-fv7m
- NVD CVE-2024-55415
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.