Authenticated code execution via executable asset upload
Published Dec 15, 2025 · Updated Dec 15, 2025
Unrestricted file upload in Perch 3.2 allows remote authenticated users with administrator access to execute server commands. The Assets edit handler accepts a .phar file as the multipart image field and stores it under the web-accessible resources path without blocking executable PHP types. Administrator control-panel access is required; requesting the stored file runs its embedded PHP with the web server's privileges.
Summary
What happened
Unrestricted file upload in Perch 3.2 allows remote authenticated users with administrator access to execute server commands. The Assets edit handler accepts a .phar file as the multipart image field and stores it under the web-accessible resources path without blocking executable PHP types. Administrator control-panel access is required; requesting the stored file runs its embedded PHP with the web server's privileges.
The record
- CVE
- CVE-2023-53889
- Published
- Dec 15, 2025
- Updated
- Dec 15, 2025
- Vendor
- Perch Runway Limited
- Product
- Perch
- Classifications
- CWE-434, T1505.003
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Dec 15, 2025CVE publishedPublication date reported by the CVE source.
- Dec 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.2
What conditions does exploitation require?
What is affected?
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
- Perch v3.2 - Remote Code Execution (RCE)proof of concept · demonstrated
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