LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes a critical remote code execution risk in Yoyager v1.4 and earlier through the media component. The record says an attacker can use a crafted PHP file to execute code. Public metadata is sparse and affected vendor/product fields are incomplete, so teams should verify whether any deployed software matches this package and version.

Executive priority

Treat as urgent if Yoyager v1.4 or earlier is present on a reachable system. The business risk is full system compromise, but the sparse public record means the first action is rapid exposure confirmation.

Technical view

CVE-2020-36070 is mapped to CWE-281 and scored CVSS 3.1 9.8: network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact. The description attributes code execution to insecure permissions around PHP file handling in the media component. No official fix details are included in the provided sources.

Likely exposure

Exposure is likely limited to internet- or intranet-accessible deployments running Yoyager v1.4 or earlier with the vulnerable media component reachable. The CVE metadata does not provide CPEs, vendor details, or deployment guidance, so asset confirmation is required.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates the issue could be exploited remotely without authentication or user interaction if a vulnerable deployment is reachable.

Researcher notes

The record references the-control-group/voyager repository, while the CVE text names Yoyager. Affected product metadata is listed as n/a, so attribution and version mapping need independent confirmation before broad conclusions.

Mitigation direction

  • Inventory applications for Yoyager v1.4 or earlier.
  • Check the project or vendor for upgrade or remediation guidance.
  • Restrict access to the media component until guidance is confirmed.
  • Prevent executable server-side scripts from running in media upload locations.
  • Review web server controls for upload and execution separation.

Validation and detection

  • Confirm whether any deployed package matches Yoyager v1.4 or earlier.
  • Verify whether the media component is enabled and reachable.
  • Review upload directories for unexpected PHP files.
  • Review server logs for unusual media-component activity.
  • Confirm compensating controls block script execution from media storage.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · low confidence lookup

CWE-281: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-36070 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-36070Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-281 · source CWE mapping

Improper Preservation of Permissions

Improper Preservation of Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.