tcg/voyager Known Vulnerabilities & Fixes
tcg/voyager has 2 known security vulnerabilities in Packagist (PHP). Review the table below for affected and fixed versions. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Is tcg/voyager in your project?
Check if you're affected by these 2 vulnerabilities.
Security Summary
- 2 affected version ranges have been identified across these 2 advisories.
- 0% of known issues have a published fixed version.
- Remediation: composer update tcg/voyager
Vulnerabilities
2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Apr 26, 2023, most recently Apr 14, 2025 (719 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2025-32931 DevDojo Voyager Argument Injection vulnerability | CRITICAL | v1.4.0, v1.4.1, v1.4.2, v1.4.3 (+6 more) | No fix available |
| CVE-2020-36070 Remote code execution in Voyager | CRITICAL | v0.11.14, v1.0.10, v1.0.11, v1.0.12 (+30 more) | No fix available |
About This Data
Vulnerability data for tcg/voyager is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related Packagist (PHP) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of tcg/voyager.