# CVE-2024-55417: DevDojo Voyager Arbitrary File Write

> Authenticated users can bypass file type checks to upload web shells, leading to arbitrary code execution on the server.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-35p2-5vrh-m3p6

## What is CVE-2024-55417?

CVE-2024-55417 is a medium-severity vulnerability in n/a, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DevDojo Voyager through version 1.8.0 is vulnerable to bypassing the file type verification when an authenticated user uploads a file via /admin/media/upload. An authenticated user can upload a web shell causing arbitrary code execution on the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-55417?

2 open source packages ship an affected version, including tcg/voyager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tcg/voyager` | Packagist | All versions to 1.8.0 | None |
| `tcg/voyager` | Packagist | All versions to 1.8.0 | None |

Products: Thecontrolgroup Voyager.

## How do I fix CVE-2024-55417?

No fix has been published for CVE-2024-55417 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-55417 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55417 exists.

Public exploit code:

- DevDojo Voyager <= 1.8.0 - Arbitrary File Write vulnerability (nuclei): http/cves/2024/CVE-2024-55417.yaml

## Other vulnerabilities in n/a

- [CVE-2020-36070](https://insights.sbomify.com/CVE-2020-36070/): Remote code execution in Voyager (critical 9.8)
- [CVE-2019-17050](https://insights.sbomify.com/CVE-2019-17050/): Path traversal in n/a (high 7.2)
- [CVE-2024-55415](https://insights.sbomify.com/CVE-2024-55415/): DevDojo Voyager vulnerable to path traversal (medium 5.7)
- [CVE-2024-55416](https://insights.sbomify.com/CVE-2024-55416/): DevDojo Voyager vulnerable to reflected Cross-site Scripting (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55417 and fix it if it is affected.

What it is: CVE-2024-55417 is a medium-severity vulnerability in n/a, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55417 exists.

Affected packages and fixed versions:
- tcg/voyager (Packagist): affected all versions up to 1.8.0; no fix listed
- tcg/voyager (Packagist): affected all versions up to 1.8.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-55417/ (Markdown: https://insights.sbomify.com/CVE-2024-55417/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-55417
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-55417
- OSV: https://osv.dev/vulnerability/CVE-2024-55417

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-55417/
Summaries are generated and may contain mistakes; the official description above is the record.