Security readout for executives and security teams
Plain-English summary
Voyager for Laravel through 1.2.7 has a weakness in Compass that can let an administrator with Compass access read or delete arbitrary server files, including Laravel’s .env file. That can expose secrets or disrupt the application. The public record does not provide a CVSS score or confirmed fixed version.
Executive priority
Prioritize systems where Voyager admin access is internet-facing, shared, or weakly controlled. The main business risk is exposure of application secrets and production disruption from file deletion, not broad unauthenticated compromise based on current evidence.
Technical view
CVE-2019-17050 affects the Voyager package through 1.2.7 for Laravel. The issue requires admin privileges and Compass access, then permits arbitrary file read or deletion. The record names .env as an example target. The only mitigation noted in the source bundle is disabling Compass in production.
Likely exposure
Exposure is limited to Laravel applications using Voyager through 1.2.7 with Compass enabled, especially in production admin panels. Risk depends on who can authenticate as an admin and whether Compass access is granted.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. This is not described as unauthenticated remote exploitation; the cited condition is an attacker with admin privileges and Compass access.
Researcher notes
Evidence is sparse: no CVSS, CWE, patch version, or detailed technical root cause is provided in the bundle. Treat the GitHub issue and CVE text as the basis, and avoid assuming affected versions beyond “through 1.2.7.”
Mitigation direction
- Disable Voyager Compass in production environments.
- Remove Compass access from nonessential administrator accounts.
- Check Voyager maintainer guidance for fixed versions or supported configuration changes.
- Protect and rotate secrets if .env may have been exposed.
- Maintain backups for files that could have been deleted.
Validation and detection
- Inventory Laravel applications using Voyager.
- Confirm deployed Voyager versions are not through 1.2.7.
- Verify Compass is disabled on production systems.
- Review admin roles for Compass permissions.
- Check logs for unusual Compass file access or deletion activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-17050 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/the-control-group/voyager/issues/4322CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.