Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2024-55417: Arbitrary File Upload and Remote Code Execution in DevDojo Voyager

Published Jan 30, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v3.1
EPSS15.9%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Thecontrolgroup
IdentifiersCVE-2024-55417CWE-434 · Unrestricted Upload of File with…

DevDojo Voyager through version 1.8.0 contains an insufficient MIME-type validation flaw in the getMimeType file-upload handling. An authenticated user with media-browsing privileges can upload a specially crafted polyglot file that bypasses file-type verification, permitting upload of arbitrary files, including PHP web shells, and resulting in arbitrary code execution on the server.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary file upload and arbitrary code execution in the server environment through an uploaded web shell.

Mitigation

If you can’t patch tonight, do this now.

Restrict media-upload access to only essential, trusted users with browse_media privileges. Until a security update is available, remove or disable the affected Voyager deployment where feasible, or replace it with an alternative product.

Remediation

Patch, then assume compromise.

No security updates were available at the time of disclosure. Administrators should avoid using the affected Voyager package or migrate to an alternative product until a vendor security patch is available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ThecontrolgroupVoyagerapplication
FAQ

Frequently asked questions

Is CVE-2024-55417 exploited in the wild?
As of Sep 30, 2026, Mallory has no reports of CVE-2024-55417 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-55417?
Yes. As of Sep 30, 2026, Mallory has reports of a public exploit for CVE-2024-55417.
Is there a patch for CVE-2024-55417?
No security updates were available at the time of disclosure. Administrators should avoid using the affected Voyager package or migrate to an alternative product until a vendor security patch is available.
What products are affected by CVE-2024-55417?
Thecontrolgroup Voyager.
How severe is CVE-2024-55417?
CVE-2024-55417 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 15.9% (97th percentile) as of Sep 30, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.