VoyagerApplication · Thecontrolgroup
CVE-2020-36070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsecure Permission vulnerability found in Yoyager v.1.4 and before allows a remote attacker to execute arbitrary code via a crafted .php file to the media component.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsecure permission controls in Voyager v1.4 and earlier allow unauthenticated remote attackers to upload malicious PHP files through the media component, achieving arbitrary code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
VoyagerApplication
< 1.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Voyager installed versionLocate the composer.json file in your Laravel project root and find the 'thecontrolgroup/voyager' entry under 'require'. Alternatively, check the version in vendor/thecontrolgroup/voyager/composer.jsonAffected if The version listed is less than 1.4.0 (e.g., 1.3.x, 1.2.x, etc.)
-
Verify media component is installed and enabledCheck your config/voyager.php configuration file for the 'media' entry under the 'components' array. Also verify the package is present in vendor/thecontrolgroup/voyager/Affected if The media component is listed as enabled in the configuration and the Voyager package files exist in the vendor directory
-
Confirm media upload endpoint is publicly accessibleExamine your routes/web.php and routes/api.php files for Voyager media routes. Check if the POST endpoint for media uploads (typically /admin/media/upload or /voyager/media) has no auth middleware appliedAffected if The media upload route exists without any authentication middleware (middleware: [] or no middleware declaration)
-
Inspect storage directory permissionsCheck the permissions on the storage/app/public directory and its subdirectories, specifically the folders where uploaded media is stored. Use ls -la storage/app/public/Affected if The storage directory is world-writable (permissions 777) or owned by a web-server-unprivileged user without proper restrictions
-
Review middleware configuration for media routesCheck the Voyager service provider or route configuration files in vendor/thecontrolgroup/voyager/src/ to determine what middleware protects the media upload routes. Compare this against your application's auth configurationAffected if No authentication or authorization middleware is required for the media upload functionality
You are affected if Voyager version is below 1.4.0 AND the media component is enabled with unauthenticated upload access exposed to the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.4.0
Upgrade Voyager to the latest patched version immediately. If upgrading is not immediately feasible, disable or restrict access to the media component and implement strict authentication on any file upload endpoints.
Voyager 1.4.0
- 1. Backup your current Voyager installation and database before proceeding with any changes.
- 2. Upgrade Voyager to version 1.4.0 or later. If using Composer, run: composer require tcg/voyager:^1.4
- 3. Clear any cached files and verify the media component is functioning correctly after upgrade.
- 4. Review user permissions for the media component to ensure proper access controls are in place.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Voyager
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-36070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data