CVE-2020-36070: Insecure Permission vulnerability found in Yoyager v.1.4 and before allows a remote attacker to execute arbitr

Q: How do I fix CVE-2020-36070?

voyager: upgrade to 1.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-36070 being exploited?

CVE-2020-36070 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-36070 affect?

CVE-2020-36070 affects voyager. Severity is critical (CVSS 9.8). Insecure 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.

Q: How urgent is CVE-2020-36070?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-36070 is a critical-severity flaw (CVSS 9.8) affecting voyager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Insecure 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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-281
Published	2023-04-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: thecontrolgroup

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-04-26 20:15 UTCPublished CVE record published
2026-06-17 03:14 UTCUpdated Record last modified

thecontrolgroup voyager UPGRADE

Affected: < 1.4.0

Fixed in: 1.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy voyager || rpm -q voyager || voyager --version

2. UPGRADE to 1.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade voyager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade voyager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36070?

voyager: upgrade to 1.4.0. Exact commands for each OS are on this page.

Is CVE-2020-36070 being exploited?

CVE-2020-36070 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36070 affect?

CVE-2020-36070 affects voyager. Severity is critical (CVSS 9.8). Insecure 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.

How urgent is CVE-2020-36070?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2024-55417 MEDIUM 4.3 UPGRADE DevDojo Voyager through version 1.8.0 is vulnerable to bypassing the file type verification when an authentica
CVE-2024-55416 LOW 3.5 UPGRADE DevDojo Voyager through version 1.8.0 is vulnerable to reflected XSS via /admin/compass
CVE-2024-55415 MEDIUM 5.7 UPGRADE DevDojo Voyager through 1.8.0 is vulnerable to path traversal at the /admin/compass.
CVE-2014-125074 MEDIUM 5.5 UPGRADE A vulnerability was found in Nayshlok Voyager

References

← Back to latest CVEs