Unauthenticated code execution via unrestricted PHP upload
Published Apr 26, 2023 · Updated Feb 3, 2025
Arbitrary code execution in Voyager 1.4.0 and earlier allows remote attackers to run PHP code by uploading a crafted file through Media. The Media component accepts a .php file without enforcing restrictions that prevent attacker-supplied PHP from becoming executable server content. No authentication or user interaction is required, and successful exploitation runs code with the web application's privileges.
Summary
What happened
Arbitrary code execution in Voyager 1.4.0 and earlier allows remote attackers to run PHP code by uploading a crafted file through Media. The Media component accepts a .php file without enforcing restrictions that prevent attacker-supplied PHP from becoming executable server content. No authentication or user interaction is required, and successful exploitation runs code with the web application's privileges.
The record
- CVE
- CVE-2020-36070
- Published
- Apr 26, 2023
- Updated
- Feb 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-281, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2023CVE publishedPublication date reported by the CVE source.
- Feb 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo