Security Resilience

CVE-2024-55415

Path Traversal in Thecontrolgroup Voyager ≤ 1.8.0

Public PoCPath Traversal
Published
30 January 2025
Modified
23 May 2025
Patch / advisory
CVSS Score v3.1 5.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.16 97th percentile
Risk Priority 70 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-55415 is a medium-severity Path Traversal (CWE-22) vulnerability in Thecontrolgroup Voyager. Its CVSS base score is 5.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

DevDojo Voyager through version 1.8.0 is affected by a path traversal vulnerability (CWE-22) at the /admin/compass endpoint. The issue carries a CVSS 3.1 score of 5.7, reflecting network attack vector, low complexity, low privileges required, and required user interaction, with high impact limited to confidentiality.

An authenticated attacker with low-privileged access can supply crafted input to the affected compass controller routes, enabling traversal outside intended directories to read arbitrary files on the server. The referenced controller implementation in VoyagerCompassController.php shows the handling logic that permits this traversal without adequate path sanitization.

Public references include source code inspection of the vulnerable controller and a SonarSource analysis detailing multiple Voyager issues, though no official patch or mitigation guidance is provided in the available references. The EPSS score stands at 0.6378 with no indicated rise from a lower baseline.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

DevDojo Voyager through 1.8.0 is vulnerable to path traversal at the /admin/compass.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-14997Shared CWE-22
CVE-2025-1543Shared CWE-22
CVE-2025-2328Shared CWE-22
CVE-2024-9362Shared CWE-22
CVE-2025-41757Shared CWE-22
CVE-2023-40274Shared CWE-22
CVE-2026-1776Shared CWE-22
CVE-2024-37169Shared CWE-22
CVE-2023-25508Shared CWE-22
CVE-2025-8343Shared CWE-22

Affected Assets

thecontrolgroup
voyager
≤ 1.8.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 partial match
blocks

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

References