Voyager 1.3.0 - Directory Traversal

The directory traversal vulnerability in Voyager CMS allows an attacker to bypass intended access controls and read arbitrary files on the server. By crafting malicious requests to the /admin/voyager-assets endpoint, an attacker can manipulate the asset path parameter to access files outside the intended asset directory. This could expose critical system configuration files, such as .env (containing database credentials, API keys, and other sensitive information) and /etc/passwd (potentially revealing user accounts). Successful exploitation could lead to complete system compromise, data breaches, and further malicious activity.

Voyager CMS installations, particularly those running version 1.3.0 or earlier, are at risk. Shared hosting environments utilizing Voyager CMS are especially vulnerable due to limited control over server configurations and potential exposure to other tenants' exploits. Development environments with default configurations are also at increased risk.

• laravel / server:

grep -r 'voyager-assets' /var/log/apache2/access.log
grep -r '..\/' /var/log/apache2/access.log

1. 2026-02-11Disclosure

   disclosure

2. 2026-02-11PoC

   poc

1. Reserviert2026-02-10
2. Veröffentlicht2026-02-11
3. Geändert2026-04-07
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2020-37214 is to upgrade Voyager CMS to version 1.3.1 or later, which contains the fix. If an immediate upgrade is not possible, consider implementing a Web Application Firewall (WAF) rule to block requests containing suspicious characters or patterns in the asset path parameter. Additionally, restrict access to the /admin/voyager-assets endpoint to authorized users only. Regularly review and harden server configurations to minimize the potential impact of this vulnerability.