Authenticated code execution via PHP asset upload
Published Mar 10, 2023 · Updated Mar 3, 2025
Unrestricted file upload in Cockpit CMS before 2.4.1 allows remote authenticated users to execute PHP code through the Assets manager. The upload handler in modules/Assets/bootstrap.php passed an allowed PHP filename to move_uploaded_file without rejecting the executable extension, placing attacker-controlled code in web-accessible asset storage. An account with asset-upload permission is required, and successful execution runs with the privileges of the web-server process.
Summary
What happened
Unrestricted file upload in Cockpit CMS before 2.4.1 allows remote authenticated users to execute PHP code through the Assets manager. The upload handler in modules/Assets/bootstrap.php passed an allowed PHP filename to move_uploaded_file without rejecting the executable extension, placing attacker-controlled code in web-accessible asset storage. An account with asset-upload permission is required, and successful execution runs with the privileges of the web-server process.
The record
- CVE
- CVE-2023-1313
- Published
- Mar 10, 2023
- Updated
- Mar 3, 2025
- Vendor
- Cockpit HQ
- Product
- Cockpit CMS
- Classifications
- CWE-434, T1505.003, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2023CVE publishedPublication date reported by the CVE source.
- Mar 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.4.1
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
- huntr.dev proof of conceptproof of concept · unverified
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